Le lundi 21 novembre 2016 14:28:11 UTC+1, Jeroen Demeyer a écrit : > > On 2016-11-21 12:37, Emmanuel Charpentier wrote: > > What do you think ? > > I think we should simply NOT install the package at all instead of > faking an install in spkg-install. We currently do for gcc and git
OK so far > using > some logic in the top-level ./configure. Aha ! Here's the rub ! You need to do this on toplevel configuration for each and every such package. This is needed for gcc, which is pretty central to any installation, and possibly for git (similar, but weaker, reasons). My point is that we should be able to do this for more mundane packages (possibly optional), without having to tinker with the toplevel config file. This is practical : - if the package does not need "in situ" Sage-specific patching, *and* - has no version-specific issues. Such a "mundane" package may need a wrapper, which can be installed separately in a separate section of the spkg-install script. (BTW : we need also to create a way to "uninstall" a Sage package more steamlined than 'make distclean && make". No ideas yet about this one...). HTH, -- Emmanuel Charpentier -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
