Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 30 Sep 2011 17:10:20 -0400
From:      Jim Trigg <jtrigg@spamcop.net>
To:        Freebsd Ports List <ports@freebsd.org>
Subject:   Re: Instafix for FreeBSD ports brokenness on 10.0?
Message-ID:  <CAJs7ybOFQrxLmKfaZbyBoP3Fhj=tibD8ZvBPKX9h4DK5EMp%2BCw@mail.gmail.com>
In-Reply-To: <20110930091002.GA1378@droso.net>
References:  <20110929084725.GN91943@hoeg.nl> <4E8433F5.30005@infracaninophile.co.uk> <20110929090743.GP91943@hoeg.nl> <20110929091859.GQ91943@hoeg.nl> <20110929134310.6585124d.stas@FreeBSD.org> <20110930084015.GV91943@hoeg.nl> <CADLo83_Z8Dp--cwUkAm4W1JFSOqkWBb3t-fP_jgNUa45yYRhww@mail.gmail.com> <20110930091002.GA1378@droso.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 30, 2011 at 5:10 AM, Erwin Lansing <erwin@freebsd.org> wrote:
> That said, this patch is the wrong place to fix a problem to autotools.
> It needs to be fixed in autotools, not bsd.port.mk. =A0No matter if it's
> bsd.ports.mk or autotools, such a fix needs proper testing, for which
> we do not currently have the resources as we are concentrating on
> releasing 9.0. =A0I would suggest you do the same and make 9.0 the best
> release possible during the next few weeks, after that we'll start
> looking into 10.0.

I have to admit that my reaction is not so much "Why won't you fix
ports for 10.0" as "Why was 9.0 dropped out of CURRENT and 10.0
introduced before 9.0 went STABLE?"

Jim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJs7ybOFQrxLmKfaZbyBoP3Fhj=tibD8ZvBPKX9h4DK5EMp%2BCw>