On Fri, Feb 24, 2017 at 10:49 AM, Jeroen Demeyer <[email protected]> wrote: > On 2017-02-24 10:31, Erik Bray wrote: >> >> On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik <[email protected]> wrote: >>> >>> one can still have something like: >>> --with-everything # build everything >>> --with-everythingneeded # build missing >>> etc... >>> to encode the most usual cases. >> >> >> Yes, I think this goes without saying. > > > And why should --with-everythingneeded *not* be the default?
I don't particularly care what the default is but the point here in the first place is that it shouldn't try to build and install its own gcc if one doesn't explicitly ask for it, opting instead to report what dependencies were missing such that sage couldn't be built. I think Simon's point was that if it can be made to work that way for gcc why stop there? Admittedly gcc is a special case. But one way or another it would be good in general to have more control over what packages Sage automatically builds and installs, as opposed to requiring dependencies from the system--this is nothing new. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
