From owner-freebsd-ports Tue Feb 15 3:45:37 2000 Delivered-To: freebsd-ports@freebsd.org Received: from mail.utexas.edu (wb3-a.mail.utexas.edu [128.83.126.138]) by builder.freebsd.org (Postfix) with SMTP id DF5C54189 for ; Tue, 15 Feb 2000 03:45:29 -0800 (PST) Received: (qmail 21418 invoked by uid 0); 15 Feb 2000 11:45:51 -0000 Received: from dial-106-4.ots.utexas.edu (HELO nomad.dataplex.net) (128.83.177.4) by umbs-smtp-3 with SMTP; 15 Feb 2000 11:45:51 -0000 From: Richard Wackerbarth To: Neil Blakey-Milner , Subject: Re: multi-level categories Date: Tue, 15 Feb 2000 05:27:33 -0600 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain Cc: FreeBSD Ports References: <20000215095852.A23520@mithrandr.moria.org> In-Reply-To: <20000215095852.A23520@mithrandr.moria.org> MIME-Version: 1.0 Message-Id: <00021505431201.07867@nomad.dataplex.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 15 Feb 2000, Neil Blakey-Milner wrote: > This seems to be easy enough using Richard's suggestion of 'ar' > archives for the patches. > > Something arb like: [ ... excellent code omitted ...] > The 'ar' archives I generated were plain-text, and we just need > some tools to convert from old-style to new-style automatically > for the people who work on the ports. This should be made an automatic part of the process. Depending on how the archiving process is used, it is no more than an extra line in the commit script. rm patches.ar ; ar -cr .patches/patch-* Note than it is important to rebuild the archive in the same order so that "diffs" in the repository are kept to a minimum. Rather than treating only the patches this way, I would apply the approach to the entire port, using the tree structure while building, but keeping only the archive the rest of the time. Either way, the archiving/dearchiving becomes just a wrapper around the checkin/checkout process. -- Richard Wackerbarth rkw@Dataplex.NET To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message