On 02/09/16 01:51, Michael Orlitzky wrote:
On 09/01/2016 09:46 AM, leif wrote:
Exactly. (See also my other reply.)
It would be dumb and totally annoying if all such packages would get
rebuilt upon *any* change to the Sage library, and just as bad as having
to "manually" figure out /which/ packages might need rebuilding after a
change to some specific part of the Sage library.
https://wiki.gentoo.org/wiki/Sub-slots_and_Slot-Operators
"Slot-operators allow the dependencies of a package to be specified such
that slot changes either will (:=) or won't (:*) trigger a rebuild of
itself."
Adding this to the package manager is a big deal, but if you're going to
do it, you might as well copy what works.
Let's talk about practical matters. I have giacpy_sage in the
sage-on-gentoo overlay already. How would you suggest to deal with this,
in this
context?
PR welcome.
Francois
--
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.
