Date: Sun, 11 Jul 1999 16:08:28 -0700 From: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> To: Nik Clayton <nik@nothing-going-on.demon.co.uk> Cc: "Daniel C. Sobral" <dcs@newsguy.com>, Nicolas Blais <nicblais@videotron.ca>, freebsd-current@FreeBSD.ORG Subject: Re: HELP!!! -CURRENT libtool problem. Message-ID: <22523.931734508@zippy.cdrom.com> In-Reply-To: Your message of "Sun, 11 Jul 1999 22:00:50 BST." <19990711220050.A31542@catkin.nothing-going-on.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Q: I want to use this cool piece of software that's in the FreeBSD > ports system. But I can't build it on my 3.x-stable system. > > Why not? A. Likely because someone running only on a -current box last committed a change to the port which broke it with 3.x. Please submit a bug report on this with send-pr since the -current ports collection is supposed to work with both the -current and -stable branches. If you're running a release version that lags significantly behind -current or -stable, you will require a ports upgrade kit from http://www.freebsd.org/ports - Jordan > > A: Ah, sorry. The ports system only targets -current, trying to get > it to work with -stable is too much work. If you want to be sure > of using the ports system successfully you need to be running > -current. > </advocate> > > Or was this policy reversed recently and I didn't notice (always a > likely possibility). > > [ And yes, I *know* the ports system relies on volunteers, and that if > people can't be bothered to test their ports on a -stable system then > there's not a lot we can do about it. But this does lead to the > amusing situation (for various values of "amusing") where on one hand > we're telling people not to use -current unless they really know what > they're doing, but on the other hand we're (in some cases) preventing > them from using a major piece of FreeBSD infrastructure which is > expressly designed to make life easier for exactly the sort of people > who should be running -stable. ] > > N > -- > [intentional self-reference] can be easily accommodated using a blessed, > non-self-referential dummy head-node whose own object destructor severs > the links. > -- Tom Christiansen in <375143b5@cs.colorado.edu> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message 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?22523.931734508>