Dear list,
We currently ship a number of packages that might duplicate the
functionality of systemwide installed libraries. My case in point : xz,
which provides support for lzma-compressed archives and a command-line tool.
What I think is that, in such cases, unless we require a very specific
version (or Sage-specific patches), we might do the following in
spkg-install :
Test for the existence of a systemwide eqivalent (executable and/or
library) ;
If positive, test for needed characteristics (version, support of
specific features);
If positive :
Display a message telling that Sage will use the systemwide
version
Set InstallNeeded=False
else
Display a message telling that Sage will build its specific version
Set InstallNeeded=Trie
Unpack the source
If InstallNeeded :
build and install the package
If test suite required
run the test suite (from the unpacked source tree)
Unless I'm mistaken, this can be done all from the spkg-install script ;
this would mark the package as installed (if the test suite runs OK),
whether or not an actual install has been done.
What do you think ?
--
Emmanuel Charpentier
--
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.
