On 03/10/2016 01:47 PM, Jeroen Demeyer wrote: > On 2016-03-10 19:23, Michael Orlitzky wrote: >> Its main issue is that all of the build >> scripts are incredibly naive. For example, the source-based install >> routing for PostgreSQL is, >> >> https://github.com/conda/conda-recipes/blob/master/postgresql-9.3/build.sh >> > > I consider the fact that build scripts are simple a feature, not a bug. > That's much better than all the "cruft" that is going into the Sage > spkg-install scripts. >
I'm not arguing that complex is better than simple, but most of their build scripts are so simple that they don't work. Error handling is nonexistent, options are hard-coded, paths are random, the environment is not sanitized, installed files are not tracked, ABI changes go unnoticed, CFLAGS are ignored, LDFLAGS are ignored,... all things we've already figured out. The Sage spkg build scripts have gotten crazy because there's no abstraction. We could almost copy the standard ebuild functions (installing files, patch application, etc.) into Sage and eliminate a ton of boilerplate if the whole thing weren't so damned Quixotic. -- 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.
