You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As observed, for example, in #31267:
Build SPKG readline, build SPKG singular (which has the dependency on readline); then removing the SPKG readline and using the system readline does not trigger a rebuild of singular.
This is caused by a shortcoming of our build system: All system packages are represented by the target $SAGE_LOCAL/var/lib/sage/installed/.dummy - which is old.
As a solution, we replace use of .dummy by separate files that represent system packages in $SAGE_LOCAL/var/lib/sage/system/....
These files can just be empty regular files, but in some cases, they could be symlinks to system files, so that an update of a system package triggers the rebuild of a Sage package.
sage.misc.package would be extended to also read these installation records.
mkoeppe
changed the title
Switching from --with-system-SPKG to --without-system-SPKG does not trigger rebuilds of dependent packages
Switching from --without-system-SPKG to --with-system-SPKG does not trigger rebuilds of dependent packages
Jan 15, 2022
As observed, for example, in #31267:
Build SPKG
readline
, build SPKGsingular
(which has the dependency onreadline
); then removing the SPKGreadline
and using the system readline does not trigger a rebuild ofsingular
.This is caused by a shortcoming of our build system: All system packages are represented by the target
$SAGE_LOCAL/var/lib/sage/installed/.dummy
- which is old.As a solution, we replace use of
.dummy
by separate files that represent system packages in$SAGE_LOCAL/var/lib/sage/system/...
.These files can just be empty regular files, but in some cases, they could be symlinks to system files, so that an update of a system package triggers the rebuild of a Sage package.
sage.misc.package
would be extended to also read these installation records.CC: @dimpase @jhpalmieri @orlitzky
Component: build
Issue created by migration from https://trac.sagemath.org/ticket/31277
The text was updated successfully, but these errors were encountered: