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