On Wed, Aug 17, 2016 at 12:43 AM, Vincent Delecroix <20100.delecr...@gmail.com> wrote: > Hi, > > On 16/08/16 09:07, Jeroen Demeyer wrote: >> >> On 2016-08-16 14:04, Erik Bray wrote: >>> >>> Hi all, >>> >>> Is there a make target for building/installing all *optional* packages >>> as well as the standard ones? >> >> >> First of all: not every optional package should be installed. There are >> packages like gmp and python3 which should not mindlessly be installed. >> >> There might be others too, like gdb on OS X doesn't work. > > > This is indeed very bad. It would be nice to be able to > install/uninstall/test packages at random without breaking the Sage install. > In particular, that would allow patchbot to test the (to be defined) subsets > of officially supported packages. And avoid (or at least make visible) > backward compatibility issues.
Indeed--as I brought up in another ticket for example there seems to be a lot of confusion about having multiple Python installations in the same environment. Done "right" this should be no problem. Installing Python 3 should not break your Python 2-based Sage installation. If it does, this means the Sage distribution needs some way to specify what the "primary" Python is (analogies to Debian's update-alternatives have been brought up) while still allowing the alternative installation on the side. Packages that simply won't work on this or that platform shouldn't install at all. Maybe there also should be a way to specify conflicting packages if it is indeed a fact (which clearly it is) that there are conflicting packages. -- 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.
