From owner-cvs-all Wed Aug 1 6:56:33 2001 Delivered-To: cvs-all@freebsd.org Received: from vega.vega.com (dialup6-28.iptelecom.net.ua [212.9.227.92]) by hub.freebsd.org (Postfix) with ESMTP id 8651E37B403; Wed, 1 Aug 2001 06:56:00 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f71DsaQ32896; Wed, 1 Aug 2001 16:54:36 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B680A3F.987975FF@FreeBSD.org> Date: Wed, 01 Aug 2001 16:55:11 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Akinori MUSHA 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 References: <200108011202.f71C2p944774@freefall.freebsd.org> <3B67F238.4A9718F3@FreeBSD.org> <86d76guft6.wl@archon.local.idaemons.org> <3B67FAEF.7E629FEA@FreeBSD.org> <86ae1jvs5d.wl@archon.local.idaemons.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit 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 Akinori MUSHA wrote: > 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. Who might know for sure what is important and what isn't? AFAIK we have cvs to keep all history, because it is impossible to tell in advance. > 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. See above. > (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... This doesn't mean that we can't do it. Currently db3-latest has no cvs history, which doesn't look like a correct thing to me. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message