Date: Mon, 7 Oct 2002 05:32:50 +0300 (EEST) From: Giorgos Keramidas <keramida@freebsd.org> To: Adam Weinberger <adam@vectors.cx> Cc: doc@freebsd.org Subject: Re: 4.7-RC error Message-ID: <20021007052616.W4202-100000@hades> In-Reply-To: <20021007004011.GC44643@vectors.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2002-10-06 17:40, Adam Weinberger wrote: > ** > i'm bringing this over from the -questions list. > ** > > why is the file called /usr/src/UPDATING? that's not a filename that a > new-ish user would check, especially when there's a README in the same > directory. kindof a misnomer IMO. The correct path is the documented path, and cutting-edge chapter of the Handbook clearly references src/UPDATING and not src/README. > makes more sense to me to move src/README to src/REAME.build, and move > src/UPDATING to src/README. or, move src/README to src/README.build and > create a new README file. one that gives very terse instructions for > building world and kernel, and possibly updating the sources. i'd be > happy to provide such a file if it sounds like a good idea. I am not against renaming src/README, but I don't really think there are good reasons to do so. The correct file to read for build instructions is already documented in the Handbook. Not having read the documentation is not a good reason for renaming files around, IMHO. Especially since I don't think that the same people who fail to read the existing documentation will also fail to read the same file if it's called README.first. Giorgos. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021007052616.W4202-100000>