Re: HELP!!! -CURRENT libtool problem.

[Satoshi - Ports Wraith - Asami]

 * From: Nik Clayton <[EMAIL PROTECTED]>

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message