On Mon, Nov 27, 2017 at 10:41 AM, Dima Pasechnik <dimp...@gmail.com> wrote: > We now have a good setup in place to make installation of an spkg > conditional on presence of a compatible one > on the system---basically, just add a dozen or two lines to configure.ac. > Examples of packages already treated this way are curl, yasm, git. gcc. > > Should there be an effort to do this for many more packages? (the 1st > obvious candidate is patch).
I have had an ongoing effort to use more system packages in a somewhat "generic" way (see https://groups.google.com/d/msg/sage-devel/nTwhCV89FXE/_7GdzGy4BgAJ) Although that thread is 6 months old, I have been working more or less on the same plan I outlined there, but the work has been stalled on what I felt was necessary preliminary work which I could use some help moving forward in terms of review... (see [1] [2] [3]). That said, although I still consider proper package uninstallation an important prerequisite to my bigger plans, that doesn't necessarily prevent us from going ahead and making more spkgs conditional on configure-time checks. One thing I might do differently from your proposal: I have some experimental code for an autoconf macro that can slurp in macros from multiple sub-directories. The idea being that you could put little .m4 files in each build/pkgs/<pkgname> dir with configure-time checks for that specific package, rather than cluttering up configure.ac with them. Perhaps I could try putting together a ticket for that...? [1] https://trac.sagemath.org/ticket/22509 [2] https://trac.sagemath.org/ticket/24106 [3] https://trac.sagemath.org/ticket/22510 -- 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.
