Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 10 Sep 1996 15:43:26 -0700 (PDT)
From:      asami@freebsd.org (Satoshi Asami)
To:        jdp@freebsd.org
Cc:        CVS-committers@freebsd.org, cvs-all@freebsd.org, cvs-ports@freebsd.org
Subject:   Re: cvs commit:  ports/lang/modula-3 Makefile ports/lang/modula-3/files mtree.in ports/lang/modula-3/pkg DESCR PLIST ports/lang/modula-3/scripts configure fix_pathnames ports/lang/modula-3/patches patch-ab patch-ac patch-ad patch-ae patch-af patch-ag patch-ah patch-ai patch-aj patch-ak patch-al patch-am patch-an patch-ao patch-ap patch-aq patch-ar patch-as patch-at patch-au patch-av patch-aw patch-ax patch-ay patch-az patch-ba patch-bb patch-bc patch-bd patch-be patch-bf patch-bg patch-aa
Message-ID:  <199609102243.PAA01349@silvia.HIP.Berkeley.EDU>
In-Reply-To: <199609100525.WAA15703@freefall.freebsd.org> (jdp)

next in thread | previous in thread | raw e-mail | index | archive | help
 *   Confession: In the original version of the Modula-3 port, I used
 *   a major version number of 353 for the shared libraries, to correspond
 *   with the SRC version number 3.5.3.  That was a dumb move -- I should
 *   have used 1.

That's quite right.  But I'm also guilty for not stopping you when you
told me to take a look at the port before import. ;)

 * 		   The current update is incompatible at the shared
 *   library level, requiring me to increment the major version number
 *   to 354, even though this is still based on SRC release 3.5.3.  This
 *   is bound to confuse some folks, unfortunately.  I weighed a number
 *   of alternatives, such as (a) cheating and going back to 1, and (b)
 *   using a 4-digit major version such as 3531.  But in the end I
 *   decided that 354 would be the best solution, even though it's
 *   confusing.

354???  Now that doesn't make much sense.  What are you going to do
when SRC releases 3.5.4?  Or if you want to make another change before 
the "real" 3.5.4 comes out?

Fortunately, this upgrade is compatible in source level (meaning cvsup
and virtualpaper users can use either this version or the older
version, and ld.so will ensure that the correct library is used), so
why don't you put on a helmet and jump back to 1?  You can add a
pre-install target that warns users loudly to remove the old version
and recompile the two utilities that require it.

Satoshi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609102243.PAA01349>