On 12/17/18 10:28 PM, Bill Allombert wrote: > >>> Does that answer your questions ? >>> >>>> + * Install libgap to /usr/lib/triplet. >>> Do you need this now ? When the interface to libgap has stabilized, then >>> probably we will split libgap from gap-dev and move it to >>> /usr/lib/triplet, but as long as it is an experimental feature it is >>> best to keep it in a subdirectory. >> I would prefer not having to apply yet another workaround to find this >> library. It is possible though. > Part of the issue is that we can little afford to go to the NEW queue to add > extra binary packages if we want to be ready before the freeze. > What do you suggest ?
If that saves us from going through NEW, I'm ok with leaving libgap in usr/lib/triplet/gap for now (assuming that we can get it to work that way). >> Would you be ok with applying these two patches? > I do not like the idea of applying SAGE-specific patches to /usr/bin/gap. > > However if we arrange for the patch to be applied only to libgap, then I > am ready to apply whatever you need. > > Cheers, Apart from libgap-api.h the two patches also add some lines to error.h, gapstate.h and gasman.h. How can we proceed? By adding a second copy of all headers to /usr/include/libgap in gap-dev? Best, Tobias
