From owner-freebsd-arch Mon Feb 12 17:48:33 2001 Delivered-To: freebsd-arch@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [209.152.133.57]) by hub.freebsd.org (Postfix) with ESMTP id 9B4F537B491 for ; Mon, 12 Feb 2001 17:48:29 -0800 (PST) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.2/8.11.1) id f1D1mSq09285 for freebsd-arch@freebsd.org; Mon, 12 Feb 2001 17:48:28 -0800 (PST) (envelope-from obrien) Date: Mon, 12 Feb 2001 17:48:28 -0800 From: "David O'Brien" To: freebsd-arch@freebsd.org Subject: Proposal on shared libs version values. Message-ID: <20010212174828.Q3038@dragon.nuxi.com> Reply-To: freebsd-alpha@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know why the participants of this will not bring this to -arch for discussion..... So I will. The proposal on the table is an allowance in our policy that in -CURRENT, a shared lib's version number may be bumped to "<-CURRENT_MAJ_VER_NUMBER>XY", where XY=00 initially when the FreeBSD major version is bumped (ie, right after a new -STABLE branch is created). [note we may want to postpone the bumping until the first non-compatible change to help keep track of which libs are incompatible with the latest -STABLE] At any point along the development of -CURRENT that a shared version bump would be helpful. One month (or so) before the -CURRENT --> -BETA change (ie, feature slush) we change the shared libs' version numbers to the next consecutive value from what is in the latest -STABLE. Opinions? -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message