From owner-freebsd-ports Wed Jul 19 7:39:45 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blues.jpj.net (blues.jpj.net [204.97.17.146]) by hub.freebsd.org (Postfix) with ESMTP id B8EF937BF98; Wed, 19 Jul 2000 07:39:40 -0700 (PDT) (envelope-from trevor@jpj.net) Received: from localhost (trevor@localhost) by blues.jpj.net (right/backatcha) with ESMTP id e6JEddI04462; Wed, 19 Jul 2000 10:39:39 -0400 (EDT) Date: Wed, 19 Jul 2000 10:39:39 -0400 (EDT) From: Trevor Johnson To: Maxim Sobolev Cc: Alexander Langer , Bill Fumerola , ports@FreeBSD.org, asami@FreeBSD.org Subject: Re: New rules for naming patches In-Reply-To: <3975AFE6.EBB9FB9@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Yes, but your message tells almost nothing about why we should need the new > naming scheme. Sorry--there is further explanation in my second message, which is archived at: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=392306+396522+/usr/local/www/db/text/2000/freebsd-ports/20000716.freebsd-ports > The update-patches target doen't seems a very strong argument > for it, because you can construct simple script telling which file each > patch-?? corresponds to and use it in this target instead. The update-patches utility supports the patch-aa-style names to a degree: if there are existing patches that are named that way, it will update them under the same names. Certainly such a script should be easy to make, but not needing one would be simpler still. :-) > Moreover conversion > from the old to the new naming cheme uavoidably will mean loosing *all* > history, because it's nearly impossible to perform such massive repo-copy, and > even if you would propose automated script that will do such repo-copy this > will mean mega repo-bloat given the current number of ports/patches. A way to avoid this is to permit the old names to still be used. Having the names of the patches reflect the names of the files being patched should help make the history more comprehensible: the patches to a particular source file will automatically go in the same ,v file as patches are created and removed over the lifetime of a port. -- Trevor Johnson http://jpj.net/~trevor/gpgkey.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message