[csw-maintainers] An idea for a shared libraries policy

Peter FELECAN pfelecan at opencsw.org
Sat Sep 25 12:48:33 CEST 2010

"Maciej (Matchek) Blizinski" <maciej at opencsw.org> writes:

> Advantages:
> - easy and complete lifecycle of shared libraries
> - phasing out of shared libraries can become part of standard catalog
> update procedures
> - simpler packages, simpler builds (no need for version modulations
> and complex merges, good for new maintainers)
> - isolation of old cruft
> - no constant re-pushing of files that aren't updated any more
> - more packages overall (good for stats!); at the same time, number of
> packages released per software upgrade remains the same.  If there
> was, say 4 packages to release with each Python update, it remains 4
> per release.  There will be just one new package.
> Disadvantages:
> - maintainers need to make more decisions when packaging
> - there's some amount of work to be done to do the transition, such as
> creation of new packages and dependencies

Excellent proposition. Plenty of advantages and the considered
disadvantages are not, in my opinion, detrimental to the overall quality
of our distribution/stack/whatever we call it. On the contrary.

More information about the maintainers mailing list