Date: Mon, 12 Jul 1999 00:31:52 -0700 (PDT) From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) To: nik@nothing-going-on.demon.co.uk Cc: cpiazza@home.net, nik@nothing-going-on.demon.co.uk, dcs@newsguy.com, nicblais@videotron.ca, freebsd-current@FreeBSD.ORG Subject: Re: HELP!!! -CURRENT libtool problem. Message-ID: <199907120731.AAA67992@silvia.hip.berkeley.edu> In-Reply-To: <19990712004612.A51439@catkin.nothing-going-on.org> (message from Nik Clayton on Mon, 12 Jul 1999 00:46:12 %2B0100) References: <37810FDD.C1321FE7@videotron.ca> <37887C61.2F462FD@newsguy.com> <19990711220050.A31542@catkin.nothing-going-on.org> <19990712155440.B494@norn.ca.eu.org> <19990712004612.A51439@catkin.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* From: Nik Clayton <nik@nothing-going-on.demon.co.uk> I really wish you would stop spreading FUD. Don't open your mouth if you don't know what you are talking about. * I was under the impression that if you were CVSup'ing the ports tree then * any changes to the ports subsystem (for example, new command line * parameters to fetch(1)) would be utilised by the ports system *before* * they had been merged in to -stable. The rationale being that if you * were tracking the ports tree in that way then you should be tracking * -current instead. The ports tree tracks *both* -current and -stable. This is the official policy. It has been this way for quite some time (and definitely from before you joined). I have never started using a new feature on -current before it was merged back to -stable (or a new feature before it was officially committed). If it happened to you, that is because you tried to use a new ports tree on an old system. The upgrade kits are your friend. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907120731.AAA67992>