From owner-freebsd-ports  Thu Jul 23 15:00:41 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id PAA12365
          for freebsd-ports-outgoing; Thu, 23 Jul 1998 15:00:41 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12332
          for <freebsd-ports@FreeBSD.org>; Thu, 23 Jul 1998 15:00:33 -0700 (PDT)
          (envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id PAA21764;
	Thu, 23 Jul 1998 15:00:01 -0700 (PDT)
Date: Thu, 23 Jul 1998 15:00:01 -0700 (PDT)
Message-Id: <199807232200.PAA21764@freefall.freebsd.org>
To: freebsd-ports@FreeBSD.ORG
From: asami@FreeBSD.ORG (Satoshi Asami)
Subject: Re: ports/7382
Reply-To: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

The following reply was made to PR ports/7382; it has been noted by GNATS.

From: asami@FreeBSD.ORG (Satoshi Asami)
To: FreeBSD-gnats-submit@FreeBSD.ORG, winter@jurai.net
Cc:  Subject: Re: ports/7382
Date: Thu, 23 Jul 1998 14:54:26 -0700 (PDT)

 I don't know if these changes should be made (leave that to the
 maintainers...), but:
 
  * lib/libpico.so.1.3 -> libpico.so.4.1 (would 4.0.1 be valid?)
 
 If the new one is incompatible with the old version, then the new one
 should be called "libpico.so.2.0" or "libpico401.so.1.0".  (Probably
 the latter, so pine3 can still be built on a system with pine4
 installed.)
 
 In no case should the shared library version number linked with the
 software's release number.  (Just think what will happen if pine-4.0.2
 comes out with an incompatible library.)
 
 Satoshi

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message