Ports completely and permanently hosed
Erich Dollansky
erich at apsara.com.sg
Fri Aug 7 01:34:32 UTC 2009
Hi,
On 07 August 2009 am 08:44:44 b. f. wrote:
> Erich Dollansky wrote:
> >I think that you hit the weakest point of FreeBSD. When a
> > version number of a base port changes, hundreds or even
> > thousands of ports have to be recompiled. It is basically the
> > same effect as when the major version number of FreeBSD
> > changes.
>
> The same is true of almost any build-from-source distribution
> that uses shared libraries, not just FreeBSD.
>
of course, this is plain logic.
> >If this would be synchronised with the main FreeBSD releases,
> > it would have a minor effect on users.
>
> But please don't attempt to slow needed development by making
> *(&@Q%#%@!!!! suggestions like this. If you need a seat-belt,
> put it on -- but don't wrap it around everyone's neck.
>
So, why is there a ports freeze just before a new release?
Isn't it done just out of the same reason?
They want to have a stable ports tree on the day of the release.
As I said, my seatbelt is the freeze whenever a basic library gets
changed.
Erich
> b.
More information about the freebsd-ports
mailing list