John Baldwin writes:
| On 14-Mar-01 Greg Black wrote:
| > "David O'Brien" writes:
| >| On Wed, Mar 14, 2001 at 12:27:02PM +1000, Greg Black wrote:
| >| > This is the point where we disagree. The information in this
| >| > file is in fact of interest to somebody who does a fresh install
| >| > from CD as the simple way to upgrade from an earlier release.
| >|
| >| Huh??? If you do a fresh install from CD, you will get a
| >| sendmail+sendmail.cf+mail.local that are all in sync and setup properly.
| >
| > I'm sure that's true; my point was that you don't get the useful
| > information that you pointed out in "/usr/src/UPDATING", since
| > that file only gets installed in some situations. I'm trying to
| > make a case for that file (or the information it contains) to be
| > part of every fresh install.
|
| Er, and how does that help someone who cvsups a newer part of the tree and
| doesn't get the newer UPDATING? :)
Sorry, I don't understand the question. I don't use cvsup and
have no plans to, so maybe I am missing something, but I don't
see why cvsup would not give you the right version of a file.
| UPDATING only makes sense within the
| context it lives in right now. If you install sbase (or maybe ssrc, whatever
| the "base source" dist is) you should get this file during sysinstall with the
| version applicable to that release. I think what you want is probably that
| some of the info in src/UPDATING be duplicated in the release notes, which is
| where the info you are referring to really belongs.
So you agree with me, the way I read this.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
