Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 27 Oct 2011 12:21:04 +0200
From:      Erwin Lansing <erwin@FreeBSD.org>
To:        freebsd-ports@freebsd.org
Cc:        current@FreeBSD.org
Subject:   Re: [UPDATE] Re: Update on ports on 10.0
Message-ID:  <20111027102104.GZ27932@droso.net>
In-Reply-To: <20111021124434.07c96389@FreeBSD.org>
References:  <20111011063602.GO68552@droso.net> <20111017153551.23281532@tetcu.info> <20111017135130.d9caa4f1.stas@FreeBSD.org> <20111018223146.GA93539@server.vk2pj.dyndns.org> <20111019105938.5aa842a4@FreeBSD.org> <20111019010420.646c0938.stas@FreeBSD.org> <20111019113136.316cb665@FreeBSD.org> <20111021124434.07c96389@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 21, 2011 at 12:44:34PM +0300, Ion-Mihai Tetcu wrote:
> > > > What, on the other hand, makes sense is to have the fix that
> > > > should include:
> > > > a) a KNOB (WITH_FBSD10_FIX or similar), 
> > > > b) that only is run from bsd.port.mk when OSVERSION>1000000
> > > > c) runs the latest version of the above patch.
> > > > The KNOB's existence allow us to turn on the fix only for broken
> > > > ports, and easily know what these broken ports are -- so we can
> > > > poke maintainers from time to time about upstream fixes, ...
> > > 
> 
> Erwin is currently running a build on i386-10 with this and the
> following patches:
> - bsd.port.mk patch from beat (based on ed@, jilles@ and stas@ patches)
> - python patch from beat
> - python patch from linimon
> - WITH_FBSD10_FIX in:
>         - textproc/expat2
>         - devel/pcre
>         - devel/libtool
>         - audio/libogg
> Results by Monday.
> 

These patches have now been committed to the tree, notably with
lang/python27 missing in the above list but was included as well.  There
have been some proposals already and we can now incrementally improve
the workaround and, more importantly, start fixing individual ports.  Please
note that the patch tries to balance between being a general enough fix
to make it easy to get a working system running while not just swiping
the whole issue under the rug and forget about it until the next release
cycle.  Make sure to send any fixes upstream to the hack can be removed
from the ports again.

Thanks for all your patience and thanks for all those involved,
especially beat who sent many patches and improvements.

Erwin

-- 
Erwin Lansing                                   http://droso.org
Prediction is very difficult
especially about the future                    erwin@FreeBSD.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20111027102104.GZ27932>