From owner-freebsd-ports Wed Jul 19 6:41:17 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blizzard.sabbo.net (blizzard.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 7A4DA37BE4E; Wed, 19 Jul 2000 06:41:06 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.106]) by blizzard.sabbo.net (8.9.1/8.9.3) with ESMTP id QAA06783; Wed, 19 Jul 2000 16:39:26 +0300 (EEST) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.9.3/8.9.3) with ESMTP id QAA97328; Wed, 19 Jul 2000 16:41:00 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3975AFE6.EBB9FB9@FreeBSD.org> Date: Wed, 19 Jul 2000 16:40:54 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Trevor Johnson Cc: Alexander Langer , Bill Fumerola , ports@FreeBSD.org, asami@FreeBSD.org Subject: Re: New rules for naming patches References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Trevor Johnson wrote: > > Please let this thread die at least until you will come with full-fledged > > patches/* proposal. > > In my message "proposal: update-patches" > (http://www.geocrawler.com/archives/3/167/2000/6/0/3964653/) I requested > that we adopt the OpenBSD folks' naming scheme, and I presented my > adaptation of their update-patches utility for generating and updating > patches with that nomenclature. If anything more is needed, please let me > know. Yes, but your message tells almost nothing about why we should need the new naming scheme. 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. 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. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message