[csw-maintainers] Upgrading shared libraries

Maciej (Matchek) Blizinski maciej at opencsw.org
Thu Sep 24 13:37:22 CEST 2009

On Thu, Sep 24, 2009 at 8:41 AM, Dagobert Michelsen <dam at opencsw.org> wrote:
> Hi Maciej,
> Am 23.09.2009 um 19:23 schrieb Philip Brown:
>> On Wed, Sep 23, 2009 at 10:05 AM, Maciej (Matchek) Blizinski
>> <maciej at opencsw.org> wrote:
>>>> every package that is "current"ly being distributed, needs to actually
>>>> WORK.
>>>> for so long as CSWbar is present, CSWlibfoo must ensure that it does
>>>> not break, by supplying the older library that CSWbar requires.
>>> That's clear. What I had in mind is: how do we prevent our libraries
>>> from growing indefinitely in size due to stale dependent packages?
> If an orphaned package depends on a legacy lib you have to keep it.
> Or update the orphaned package yourself or find somebody.

I see. Too bad, that's a complication I had hoped was possible to avoid.

I revisited the modulation presentation from Oslo, it looks like I
need to learn more on how to do create multi-version library packages.
I'll try to find time this weekend to see if I get this to work. I'm
thinking of creating a mgar/pkg/examples directory and putting there a
few minimal examples, similar to minimalsmf.


More information about the maintainers mailing list