From owner-cvs-all Wed Aug 1 5:50:34 2001 Delivered-To: cvs-all@freebsd.org Received: from vega.vega.com (dialup5-21.iptelecom.net.ua [212.9.227.21]) by hub.freebsd.org (Postfix) with ESMTP id 5C32137B401; Wed, 1 Aug 2001 05:50:14 -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 f71CnFQ32743; Wed, 1 Aug 2001 15:49:15 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B67FAEF.7E629FEA@FreeBSD.org> Date: Wed, 01 Aug 2001 15:49:51 +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> 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:12:40 +0300, > sobomax wrote: > > Akinori MUSHA wrote: > > > > > knu 2001/08/01 05:02:51 PDT > > > > > > Modified files: > > > databases Makefile > > > Added files: > > > databases/db3-latest Makefile distinfo pkg-comment pkg-descr > > > pkg-plist > > > databases/db3-latest/files patch-aa patch-ab > > > Log: > > > Add db3-latest, the latest version of databases/db3, 3.3.11. > > > > What about repo-copy? > > I don't think we need one. It will never replace databases/db3 and > any the essential update will gradually be merged into db3, so the > history will not be lost. > > Am I missing something? 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 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. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message