Date: Mon, 14 Feb 2000 23:41:42 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Jeremy Lea <reg@FreeBSD.ORG> Cc: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG>, FreeBSD Ports <ports@FreeBSD.ORG> Subject: Re: multi-level categories Message-ID: <20000214234142.E76484@dragon.nuxi.com> In-Reply-To: <20000214202034.A85452@shale.csir.co.za>; from reg@FreeBSD.ORG on Mon, Feb 14, 2000 at 08:20:34PM -0800 References: <vqc4scoddtw.fsf@silvia.hip.berkeley.edu> <XFMail.000108122747.andrews@TECHNOLOGIST.COM> <20000108131719.A22210@futuresouth.com> <vqc66wrnxqb.fsf@silvia.hip.berkeley.edu> <20000118172055.D457@argon.blackdawn.com> <vqcitzshzr9.fsf@silvia.hip.berkeley.edu> <20000214202034.A85452@shale.csir.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 14, 2000 at 08:20:34PM -0800, Jeremy Lea wrote: > Make COMMENT the first line of DESCR. It is anyhow in about 40% of the > ports, and it means that there is only one file like this to maintain. > It's pretty easy to 'head -n 1 DESCR'. This would save 3069 files. That is a very good idea! > There's at least one very good reason not to do this. security/pgp. > Sometimes you need two patch sets. And although I don't think we have > any patches.i386 and patches.alpha yet, they'll come... What patches would be different for the i386 and the Alpha that can't be dealt with using "#ifdef __i386__" or "#ifdef __alpha__" ? > I think that having support for more than one patches dir might be nice > (especially for ports using MASTERDIR). I haven't needed it for any of my ports and many of them are master-slave types. > Having one patch per file makes it more difficult to determine if a file > is already being patched, Why? ``fgrep foo.c patch-*'' is broken or something? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000214234142.E76484>