| 1 |
On 08/21/2011 01:07 PM, Petteri Räty wrote: |
| 2 |
> On 21.08.2011 15:27, Michał Górny wrote: |
| 3 |
>> On Sun, 21 Aug 2011 07:29:45 -0400 |
| 4 |
>> "Anthony G. Basile" <basile@××××××××××××××.edu> wrote: |
| 5 |
>> |
| 6 |
>>> OpenSuse has a nice solution. After an upgrade, it tells you that |
| 7 |
>>> there are some running binaries still linking against the old |
| 8 |
>>> libraries and asks you to run "zypper ps" to see them in a pretty |
| 9 |
>>> format. You can then restart at your discretion. |
| 10 |
>>> |
| 11 |
>>> I'm wondering if we should add something like that? Something to be |
| 12 |
>>> run post_inst() and just ewarn the user. It could be a small eclass |
| 13 |
>>> on its own that maintainers can elect to inherit and use in ebuilds |
| 14 |
>>> for daemons. |
| 15 |
>>> |
| 16 |
>>> What do you think? If its a good idea, is implementing it in an |
| 17 |
>>> eclass the way to go? |
| 18 |
>> Rather in PM. Portage 2.2 already does some library magic due to |
| 19 |
>> preserved-libs, why it can't do something in this area too? |
| 20 |
>> |
| 21 |
> Yeah seems like something a package manager can implement and wouldn't |
| 22 |
> necessarily need anything from ebuilds. |
| 23 |
> |
| 24 |
> Regards, |
| 25 |
> Petteri |
| 26 |
> |
| 27 |
|
| 28 |
Agreed for the above reason. I'm not too familiar with portage |
| 29 |
internals. If this is an easy addition for you guys, do you mind doing |
| 30 |
it? Otherwise I'll try to produce a patch. |
| 31 |
|
| 32 |
-- |
| 33 |
Anthony G. Basile, Ph.D. |
| 34 |
Gentoo Linux Developer [Hardened] |
| 35 |
E-Mail : blueness@g.o |
| 36 |
GnuPG FP : 8040 5A4D 8709 21B1 1A88 33CE 979C AF40 D045 5535 |
| 37 |
GnuPG ID : D0455535 |
Archives