Date: Sun, 3 Aug 1997 23:08:55 +0300 (EEST) From: Penisoara Adrian <ady@warp.starnets.ro> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: current@FreeBSD.ORG Subject: Re: ports-current/packages-current discontinued Message-ID: <Pine.BSF.3.96.970803225315.942A-100000@ady.warp.starnets.ro> In-Reply-To: <2847.870634281@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Sun, 3 Aug 1997, Jordan K. Hubbard wrote: > sites, it's the most popular download target. The folks who run > -current are another breed, and I think it's also safe to say that > they're the most capable of building their own packages and/or > adapting ports to their use (and if they're not so capable, they > probably should not be running -current in the first place). Hmm, seems like I'm gonna blame myself one day for sticking with -current, but I hope it won't be so bad... OK then, how about preserving one of the latest 'stable' -current ports branch (sounds nasty, heh ?) and stick it somewhere along with the official ports brach, or even somewhere more obscure, but at least to be available ? For example, in my case, I'll install 3.0-970718-SNAP and won't follow -current [until it will stabilize again], so I'll badly need these ports... > We have shown an alarming tendency up to now to "oversell" -current as > the place to be and I see this as a very dangerous practice, only to > become all the more dangerous once we start seriously wading in with > the multiple platforms and (I think this is becoming a foregone > conclusion) ELF support. Trying to match -current's rate of change in > the ports collection is nothing more than a recipe for insanity and > premature death among our ports team and I also think it's a waste of > their time and abilities. Up until now we've had it exactly > *backwards* in our policy of supporting -current and dropping support > for the release branch quickly (something which has created a lot of > ill-will in the user base, I might add, as reading USENET will show) > and when I read Satoshi's announcement that he was dropping support > for -current, I felt no dismay at all. I've always regarding this as > inevitable, and having more attention paid to our release branch as a > result can only be a good thing for the majority of our user base. Well, you're right; from what I see these days' -current seems like everybody's playground, so it's understandable that ports support for it will be cut down for a while (I assume sometime later -current will gain back ports support). You're right Jordan, and I cannot blame anyone for this; it's development evolution... Ady (@warp.starnets.ro)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.970803225315.942A-100000>