On Sat, Feb 21, 2015 at 03:58:29AM -0800, Volker Braun wrote: > [..] it still doesn't work.
you keep saying that. but does it matter? the configuration worked pretty good as a proof-of-concept. i am sorry if your expectations were higher. note that this particular part was just optional within the project ([1] part 2, last item), no more no less. as it seems, hardly anybody (and about zero of the core developers) from the sage community wants to make use of system-installed packages (except for maybe gcc, ssl and whatnot). yet, i did not expect that much headwind. after all the mere attempt of a straightforward bypass implementation has been pretty pointless. in the meantime, i have dropped the top-level part to concentrate on making just sage (the library, the software, the essential part) work for non-(sage-the-distribution or OSX-based) software distributions. the effort makes no sense for sage-the-distribution, where all paths are to stay static and hardcoded. forks are evil and all that, but the build/install now works if the build dependencies are available. it's lagging behind at 6.3-something, i don't use sage currently, and i have other things to do. > Nor is it a particularly good way of exposing a lot of configuration > options (at least one per package). the intent was to have exactly one option per package. this (would have) allowed to install/develop sage-the-distribution with all foreign packages disabled except pari (hey, this is not even off topic!). may anyone find a better way. good luck felix [1] https://www.google-melange.com/gsoc/project/details/google/gsoc2013/felixs/5779342353235968 -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
