From owner-cvs-all Wed Aug 1 8: 0:27 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 EC8E737B401; Wed, 1 Aug 2001 08:00:19 -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 C0C5C4D801; Thu, 2 Aug 2001 00:00:17 +0900 (JST) Date: Thu, 02 Aug 2001 00:00:17 +0900 Message-ID: <868zh3vn9a.wl@archon.local.idaemons.org> From: "Akinori MUSHA" To: Maxim Sobolev Cc: osa@freebsd.org.ru, 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: <3B680A3F.987975FF@FreeBSD.org> 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> <3B680A3F.987975FF@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 16:55:11 +0300, sobomax wrote: > > At Wed, 01 Aug 2001 15:49:51 +0300, > > sobomax wrote: > > 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 It's all up to the overall build cycle of the ports tree. Many maintainers delay their ports update and skip versions when it breaks other ports. Now I'd like to hear from the maintainer of the port in question. :) > keep all history, because it is impossible to tell in advance. See the other cases where we have foo and foo-devel at the same time. > This doesn't mean that we can't do it. We never overwrite or incrementally copy files' history because of CVS's limitations. > Currently db3-latest has no cvs history, > which doesn't look like a correct thing to me. Since db3 will never die before db3-latest, the recopied part would just be duplicate, redundant bloat, IMO. -- / /__ __ 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