[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Rules for shared libraries in the ports tree
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Rules for shared libraries in the ports tree
- From: Marc Espie <espie_(_at_)_schutzenberger_(_dot_)_liafa_(_dot_)_jussieu_(_dot_)_fr>
- Date: Thu, 1 Nov 2001 13:37:43 +0100
- Mail-followup-to: ports_(_at_)_openbsd_(_dot_)_org
- Reply-to: Marc_(_dot_)_Espie_(_at_)_liafa_(_dot_)_jussieu_(_dot_)_fr
The ports tree is going to be tracking shared libraries more accurately.
As a result, all porters who maintain ports with shared libraries *MUST*
be aware of the version number rules.
- incompatible change in API (removing functions, changing functions) ->
major number bump.
- compatible change in API (mostly adding new functions, pretty much
everything else is out) -> minor number bump.
Note that most software authors don't have a clue about this. If you end
up having a libfoo.so.1.2 just because the foo package is at version 1.2,
well, there's a good thing something is seriously wrong.
The idea is that, pretty soon, packages are going to be exactly as picky
as they must be to handle dependent shared libraries.
In order to help maintainers do the right thing, I will try to check
all ports update that involve shared libraries, and I will immediately
mark BROKEN any port that does not respect the rules...