Durch die erste zweistellige Versionsnummer in FreeBSDs Geschichte hat es leider die Ports zerrissen. Die guten GNU Autotools nehmen eine einstellige Nummer an und versagen, wenn sie größer ist. Sie halten FreeBSD 10 stattdessen für das 1993 erschienene FreeBSD 1... Das zu beheben benötigt größere Eingriffe in das Ports-System und aus Stabilitätsgründen werden diese nicht passieren, bevor 9.0-RELEASE veröffentlicht wurde. Für die Praxis bedeutet es, dass die Ports bis dahin auf 10-CURRENT (Alle anderen Zweige - 7.x, 8.x und 9.x - sind nicht betroffen!) nicht funktionieren werden! Nutzer von CURRENT sollten sich daher überlegen, ob sie nicht für längere Zeit auf Updates verzichten oder im neuen RELENG_9 Zweig bleiben.
Dazu noch eine Begründung, weshalb man sich mit der Reparatur Zeit lässt:
Code:
From: Ade Lovett <ade@FreeBSD.org>
To: ports@FreeBSD.org, current@FreeBSD.org
Cc:
Reply-To: ade@FreeBSD.org
Subject: HEADS UP: ports/ and 10.0-CURRENT
Date: Mon, 26 Sep 2011 23:03:35 -0500
Sender: owner-freebsd-current@freebsd.org
X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0)
With the advent of the conversion of HEAD to 10.0-CURRENT and, as to be
expected, ports/ is going to be essentially unusable for a while.
The issue stems from configure scripts (to choose something completely
at random) assuming that FreeBSD would never jump to a double-digit
major version number, and as such, various regexps for "freebsd1*" (ie:
FreeBSD 1.1.x) are now matching "freebsd10".
This is going to be some fairly fundamental breakage.
However, until such time as 9.0-RELEASE is completely out of the door,
with autotools hat on, I will _not_ be committing any changes to
infrastructural ports to "fix" this.
That is to say, until 9.0-R happens, and for some considerable period
afterwards, ya'll can pretty much expect ports/ to be non-functional on
HEAD. PRs mentioning this will be gleefully closed referencing this
message.
-aDe
Reply-To set to me. Please honor it.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Dazu noch eine Begründung, weshalb man sich mit der Reparatur Zeit lässt:
Code:
From: Ade Lovett <ade@FreeBSD.org>
To: ports@freebsd.org, current@freebsd.org
Cc:
Subject: Re: HEADS UP: ports/ and 10.0-CURRENT
Date: Tue, 27 Sep 2011 01:29:02 -0500
Sender: owner-freebsd-current@freebsd.org
X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd9.0)
> It just means that folks didn't plan ahead and didn't think up
> proper contingency plans.
First off, apologies to Garrett, I'm not picking on you directly, but I
kinda knew this would come up.
The undeniable fact is that configure scripts in general have chosen to
do things a certain way. Unfortunately for us (us being FreeBSD), we
have now broken these conceptions by moving to a dual-digit major
release.
Emails have been passed around (somewhere starting around the 7.x
series when it became obvious we would be hitting 10.x a lot sooner
than expected). It is no-one's fault that 23,000+ third party
applications couldn't be tweaked prior to a trivial change
in /sys/conf/newvers.sh that resulted in this "oops".
The message I wanted to set across is that until such time as us ports
folks have had a chance to really work out the damage, and start on
fixing it, then for those running 10-CURRENT, things are likely to be
non-linear for a while.
Our primary responsibility right now is to ensure that a proper set of
packages gets built for the impending 9.0-RELEASE. We haven't
forgotten you bleeding edge folks, it's just that right now, you're
somewhat down the food chain.
Make no mistake. This move to a double-digit major version number is
going to cause serious pain. We will do our best to fix, hack, slash,
and whatever around it, but right now the focus is the last of our
remaining single-digit releases. Until that is out the door, do not be
expecting tree-wide commits to fix things.
-aDe
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Last edited: