On Sun, Jul 11, 1999 at 10:00:50PM +0100, Nik Clayton wrote:
> <advocate type="devils">
hmm...
<snip>
> >
> > Any other question?
>
> 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: 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).
Um..er... I hope you were really just being sarcastic. All ports
should work on -stable as well as -current. In fact, more build
on -stable than -current according to http://bento.freebsd.org/.
If any ports work on one but not the other it is a bug and should
be fixed. So I ask, what policy?
>
> [ 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. ]
-Chris
--
[EMAIL PROTECTED] [EMAIL PROTECTED]
"A great many people think they are thinking when
they are merely rearranging their prejudices"
-William James
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
