[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CVS: cvs.openbsd.org: ports
- To: Brad Smith <brad@cvs.openbsd.org>, kevlo@openbsd.org
- Subject: Re: CVS: cvs.openbsd.org: ports
- From: Marc Espie <espie@schutzenberger.liafa.jussieu.fr>
- Date: Mon, 4 Dec 2000 17:58:04 +0100
- Cc: ports@openbsd.org
- Content-Disposition: inline
- Mail-Followup-To: Marc Espie <espie@schutzenberger.liafa.jussieu.fr>,Brad Smith <brad@cvs.openbsd.org>, kevlo@openbsd.org,ports@openbsd.org
- References: <200012041600.eB4G0VJ01482@cvs.openbsd.org>
- User-Agent: Mutt/1.2.5i
On Mon, Dec 04, 2000 at 09:00:31AM -0700, Brad Smith wrote:
> CVSROOT: /cvs
> Module name: ports
> Changes by: brad@cvs.openbsd.org 2000/12/04 09:00:30
>
> Modified files:
> devel/popt : Makefile
> devel/popt/pkg : PFRAG.shared
> Added files:
> devel/popt/patches: patch-Makefile.in
>
> Log message:
> Bump shared library minor rev number; requested by espie@
Thanks.
Actually, this is somewhat of an old rule that becomes more and more
important.
Very soon, we will have to deal with package updates. Among other things,
this means that library version numbers have to be consistent.
Specifically, bug-fixes -> no version number change.
API additions -> minor bump.
API changes (old function removed, real interface changes) -> major bump.
In the past, we have managed to somehow get away with not doing it because
our dependency system is utterly silly and too strict.
Assuming I manage to get pkg update up and running, we ARE going to end up
with systems with new packages installed, and remnants of old packages
(especially shared libraries) still being around.
Hence, not following the correct rules for shared library version number
is going to be deadly...
So porters should now be very careful about these.