| 1 |
On 12/20/2012 12:35 PM, Pacho Ramos wrote: |
| 2 |
> El jue, 20-12-2012 a las 12:23 -0800, Zac Medico escribió: |
| 3 |
>> On 12/20/2012 12:09 PM, Rich Freeman wrote: |
| 4 |
>>> On Wed, Dec 19, 2012 at 4:43 AM, Zac Medico <zmedico@g.o> wrote: |
| 5 |
>>>> On 12/18/2012 11:58 PM, Duncan wrote: |
| 6 |
>>>>> I didn't know that. Last I knew, stable portage had special-case |
| 7 |
>>>>> acceptance of @system and @world to prepare the way, but I hadn't seen |
| 8 |
>>>>> that full /etc/portage/sets/* and /var/lib/portage/world_sets support was |
| 9 |
>>>>> stabilized. |
| 10 |
>>>>> |
| 11 |
>>>>> If indeed it is as you say, I've even more to rejoice about! =:^) |
| 12 |
>>>> |
| 13 |
>>>> Yeah, it's only been in stable for a few months now, so lots of people |
| 14 |
>>>> aren't aware of it yet. |
| 15 |
>>>> |
| 16 |
>>>> The current list available in portage-2.1.10.x, reported by emerge |
| 17 |
>>>> --list-sets is: |
| 18 |
>>>> |
| 19 |
>>>> preserved-rebuild |
| 20 |
>>> |
| 21 |
>>> If @preserved-rebuild and the corresponding FEATURES=preserve-libs are |
| 22 |
>>> now stable, we should create a news item about this. |
| 23 |
>>> |
| 24 |
>>> Otherwise people will still be running revdep-rebuild a decade from |
| 25 |
>>> now, as this feature was never formally announced as far as I'm aware, |
| 26 |
>>> and all the mentions of it were ages ago and not available to stable |
| 27 |
>>> users at the time. |
| 28 |
>> |
| 29 |
>> It's not enabled by default yet though. In the following blog post I've |
| 30 |
>> mentioned that I would like to wait for EAPI 5 and automatic rebuilds |
| 31 |
>> (via sub-slots and slot-operators) to gain widespread adoption before |
| 32 |
>> preserve-libs is enabled by default: |
| 33 |
>> |
| 34 |
>> http://blogs.gentoo.org/zmedico/2012/09/21/preserve-libs-available-in-portage-2-1/ |
| 35 |
>> |
| 36 |
>> The reason that I want to wait is that EAPI 5 automatic rebuilds provide |
| 37 |
>> solutions for known problems with @preserved-rebuild. These problems |
| 38 |
>> include symbol collisions [1] and unnecessary rebuilding of packages |
| 39 |
>> that are eligible for removal by emerge --depclean [2]. |
| 40 |
>> |
| 41 |
>> [1] |
| 42 |
>> http://blog.flameeyes.eu/2008/06/a-few-risks-i-see-related-to-the-new-portage-2-2-preserve-libs-behaviour |
| 43 |
>> [2] https://bugs.gentoo.org/show_bug.cgi?id=364425 |
| 44 |
> |
| 45 |
> Regarding symbol collisions, they would appear when people don't rebuild |
| 46 |
> packages after updating (and that would be solved with eapi5, no? But, |
| 47 |
> it's not exactly the same as is occurring currently if people forget to |
| 48 |
> run revdep-rebuild (or if it's partially run)? |
| 49 |
|
| 50 |
The problem with symbol collisions is only possible for people who have |
| 51 |
preserve-libs enabled. On the other hand, when preserve-libs is |
| 52 |
disabled, programs simply fail to run due to the libraries that they |
| 53 |
linked against having been unmerged when the library was updated. |
| 54 |
-- |
| 55 |
Thanks, |
| 56 |
Zac |
Archives