From owner-freebsd-current Mon Jul 12 0:32:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from dfw-ix15.ix.netcom.com (dfw-ix15.ix.netcom.com [206.214.98.15]) by hub.freebsd.org (Postfix) with ESMTP id 67802151D8 for ; Mon, 12 Jul 1999 00:32:50 -0700 (PDT) (envelope-from asami@cs.berkeley.edu) Received: (from smap@localhost) by dfw-ix15.ix.netcom.com (8.8.4/8.8.4) id CAA05614; Mon, 12 Jul 1999 02:32:14 -0500 (CDT) Received: from sji-ca4-70.ix.netcom.com(205.186.212.198) by dfw-ix15.ix.netcom.com via smap (V1.3) id rma005543; Mon Jul 12 02:31:59 1999 Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id AAA67992; Mon, 12 Jul 1999 00:31:52 -0700 (PDT) Date: Mon, 12 Jul 1999 00:31:52 -0700 (PDT) Message-Id: <199907120731.AAA67992@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f 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 In-reply-to: <19990712004612.A51439@catkin.nothing-going-on.org> (message from Nik Clayton on Mon, 12 Jul 1999 00:46:12 +0100) Subject: Re: HELP!!! -CURRENT libtool problem. From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) 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> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Nik Clayton 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