Date: 18 Jan 2000 08:36:12 -0800 From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: "Matthew D. Fuller" <fullermd@futuresouth.com> Cc: Will Andrews <andrews@TECHNOLOGIST.COM>, ports@FreeBSD.ORG Subject: Re: multi-level categories Message-ID: <vqc66wrnxqb.fsf@silvia.hip.berkeley.edu> In-Reply-To: "Matthew D. Fuller"'s message of "Sat, 8 Jan 2000 13:17:19 -0600" References: <vqc4scoddtw.fsf@silvia.hip.berkeley.edu> <XFMail.000108122747.andrews@TECHNOLOGIST.COM> <20000108131719.A22210@futuresouth.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: "Matthew D. Fuller" <fullermd@futuresouth.com>
* In at least most cases, I support this anyway :)
* I remember taking 20 minutes to track down Mosaic, simply because it was
* capitalized for no real reason I could discern..
Yes. The same goes for package names, but that's already covered in
the handbook (and there has been the rule about package names ever
since I became PW, err, ports manager).
* > Why wouldn't it be a Good Idea? Can't we just patch using a patch-* regex in
* > ${.CURDIR}?
*
* Making it machine-readable is trivial. Making reading 'ls' palpable is
* harder.
Yes, that was what I meant. Thanks.
* I'm trying to think of a good reason why files/, scripts/, and patches/
* can't all be combined into files/. That's what they all are, anyway...
I'd like to keep scripts/ separate because names of the files in that
directory are significant. I don't want someone putting his own
"configure" script in files/, intending to be copied to ${WRKSRC},
only to have it been run automatically from bsd.port.mk. ;)
Besides, not many ports have scripts/ anyway. And the #1 reason why I
wanted to move md5 out of files/ was because that will get rid of the
files/ dir on most of the ports, giving you this standard picture
(requoted):
> 1 CVS/ 1 Makefile 1 PKGCOMMENT
> 1 PKGDESCR 6 PKGPLIST 1 md5
> 1 patches/
* AFA filesystem performance it would make a BIG difference. All ports
* have files/, and a large number (most?) have patches/. I'd say that
* sticking everything in files/ would cut the number of dirs practically
* in half. Yay, a /usr/ports that uses a less-than-obscene number of
* inodes!
For a port without patches, my suggestion (move md5 out of files/,
leave patches/ alone) will make it even less. :)
Of course, we can move md5 out of files/ *and* move patches into
files/, but I'm not sure how much this will buy us. Also, I keep
copies of private patches in files/, aren't there others who do this?
* sink. Even musca (my 2.1.5 386/16 with 4 megs of RAM) can handle that
* in a fairly trivial amount of time.
Don't tell me that's where you build your ports....
-PW
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?vqc66wrnxqb.fsf>