On Mon, Jul 12, 1999 at 12:46:12AM +0100, Nik Clayton wrote: > > 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 Well, ya, sometimes that happens, especially if you CVSup only the ports tree. The upgrade kits found on http://www.FreeBSD.org/ports/ are useful here. -- This is my .signature which gets appended to the end of my messages. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: HELP!!! -CURRENT libtool problem. Sheldon Hearn
- Re: HELP!!! -CURRENT libtool probl... Warner Losh
- Re: HELP!!! -CURRENT libtool problem. Doug
- Re: HELP!!! -CURRENT libtool problem. Bradley T. Hughes
- Re: HELP!!! -CURRENT libtool problem. David O'Brien
- Re: HELP!!! -CURRENT libtool problem. Jeremy Lea
- Re: HELP!!! -CURRENT libtool problem. Daniel C. Sobral
- Re: HELP!!! -CURRENT libtool problem. Nik Clayton
- Re: HELP!!! -CURRENT libtool probl... Chris Piazza
- Re: HELP!!! -CURRENT libtool p... Nik Clayton
- Re: HELP!!! -CURRENT libto... Tim Vanderhoek
- Re: HELP!!! -CURRENT libto... Satoshi - Ports Wraith - Asami
- Re: HELP!!! -CURRENT ... Nik Clayton
- Re: HELP!!! -CURR... David O'Brien
- Re: HELP!!! -CURRENT libtool probl... Jordan K. Hubbard
- Re: HELP!!! -CURRENT libtool p... Kris Kennaway
- Re: HELP!!! -CURRENT libto... Doug White
- Re: HELP!!! -CURRENT libto... John Baldwin
- Re: HELP!!! -CURRENT libtool probl... Adam Strohl
- Re: HELP!!! -CURRENT libtool probl... David O'Brien