Robert Anderson <[EMAIL PROTECTED]> writes: > *.o, *.a, etc. should be precious and not unrecognized patterns by > default. To do otherwise is to simply annoy new users in a sort of > obfuscated meta-rant about how their build treats "ought to be" > constructed. Counterproductive. > > "unrecognized" is a poor name for that category and should be changed > to something like "disallowed" or "block". They are perfectly well > recognized, and recognized for something specific. Express what that > something is. > This is a sentiment shared by Andy Wingo; from his blog[0]:
,---- | I feel like I've been living with Tom Lord for the last nine | months. It's like he's over my shoulder, telling me what to name my | files, how to build my software, and how to deal with revision | control. `---- :-D Read the full blog entry if you're interested, he's also got to say good things about Arch. While I personally like the "keep your tree clean" attitude of Arch, I think it would be a good thing to make it a bit friendly to people who *don't* want that strictness level (while being keeping the ablity to restrict oneself, if one feels like it). [0] http://wingolog.org/archives/2004/10/01/nine-months-with-arch Cheers, Rotty -- Andreas Rottmann | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://yi.org/rotty | GnuPG Key: http://yi.org/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 Say NO to Software Patents! -- http://petition.eurolinux.org/ _______________________________________________ Gnu-arch-users mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/
