Michael Orlitzky posted on Mon, 22 Jan 2018 10:04:30 -0500 as excerpted: > On 01/22/2018 05:10 AM, Duncan wrote: >>>> >>>> If the dependencies are to remain in the eclasses, then the eclasses >>>> should get a new revision when those dependencies change. Afterwards, >>>> the consumers can be revbumped and stabilized normally to utilize the >>>> new eclass. >>> >>> Sounds good! >> >> How does that work with live-vcs ebuilds, aka -9999 ebuilds? >> >> > It doesn't. As with upstream code changes, you have to figure out > yourself when it's time to re-emerge a live ebuild.
Thanks for the confirmation. Hmm... I wonder if @smart-live-rebuild could (without /too/ much trouble) be made to detect upgraded deps, comparing the live repo version against what's in /var/db/pkg/, as it already does for upstream changes? If it already has the feature I've not seen any indication of it from the output. All the updates I've seen appear to be due to upstream repo updates. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
