From owner-cvs-all Wed Aug 1 6:14:57 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.musha.org (daemon.musha.org [61.122.44.178]) by hub.freebsd.org (Postfix) with ESMTP id 5DDE337B401; Wed, 1 Aug 2001 06:14:41 -0700 (PDT) (envelope-from knu@iDaemons.org) Received: from archon.local.idaemons.org (archon.local.idaemons.org [192.168.1.32]) by mail.musha.org (Postfix) with ESMTP id 2AE4A4DC7C; Wed, 1 Aug 2001 22:14:39 +0900 (JST) Date: Wed, 01 Aug 2001 22:14:39 +0900 Message-ID: <86ae1jvs5d.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: Maxim Sobolev Cc: Akinori MUSHA , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: ports/databases Makefile ports/databases/db3-latestMakefile distinfo pkg-comment pkg-descr pkg-plistports/databases/db3-latest/files patch-aa patch-ab In-Reply-To: <3B67FAEF.7E629FEA@FreeBSD.org> References: <200108011202.f71C2p944774@freefall.freebsd.org> <3B67F238.4A9718F3@FreeBSD.org> <86d76guft6.wl@archon.local.idaemons.org> <3B67FAEF.7E629FEA@FreeBSD.org> User-Agent: Wanderlust/2.7.1 (Too Funky) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-1?Q?Unebigory=F2mae?=) APEL/10.3 MULE XEmacs/21.1 (patch 14) (Cuyahoga Valley) (i386--freebsd) Organization: Associated I. Daemons X-PGP-Public-Key: finger knu@FreeBSD.org X-PGP-Fingerprint: 081D 099C 1705 861D 4B70 B04A 920B EFC7 9FD9 E1EE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At Wed, 01 Aug 2001 15:49:51 +0300, sobomax wrote: > Yes, you do (IMO). Imagine that tomorrow new version is released (say > 3.3.12), while compatibility problem is still here, so you are updating > db3-latest and leaving db3 as is. Eventually, after some time, the > problem that lead to db3/db3-latest fork disappears, so you have to merge > db3-latest back into db3 and delete the former, but at this point > db3-latest already accumulated some history (our imaginary 3.3.11 --> > 3.3.12 upgrade and possibly others deltas), so you have to select > whicheve history to dump - db3 or db3-latest. This problem will not exist The 3.3.11 -> 3.3.12 upgrade history would not be important because 3.3.x will never become our recommended version until it's pulled down to databases/db3. I had a good mind to name it databases/db3-devel, but I decided not since db 3.3.11 was actually a release from Sleepycat. However, from the ports point of view it's still a development version and databases/db3-latest will preverse the history of the maturing periods. (I wouldn't insist on it, though) > if you did a repo-copy from db3 to db3-latest at the beginning - in this > case you are simply doing a repo-delete of db3 and repo-copy from > db3-latest back to db3. I've never heard we ever did something like that... -- / /__ __ Akinori.org / MUSHA.org / ) ) ) ) / FreeBSD.org / Ruby-lang.org Akinori MUSHA aka / (_ / ( (__( @ iDaemons.org / and.or.jp "Freeze this moment a little bit longer, make each impression a little bit stronger.. Experience slips away -- Time stand still" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message