Date: Sat, 20 Sep 2003 23:57:23 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: jb@cimlogic.com.au Cc: h@schmalzbauer.de Subject: Re: ports and -current Message-ID: <20030920.235723.32536816.imp@bsdimp.com> In-Reply-To: <20030921051525.GA31537@freebsd1.cimlogic.com.au> References: <20030920.204425.25098720.imp@bsdimp.com> <Pine.GSO.4.10.10309210106070.26520-100000@pcnet5.pcnet.com> <20030921051525.GA31537@freebsd1.cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20030921051525.GA31537@freebsd1.cimlogic.com.au>
John Birrell <jb@cimlogic.com.au> writes:
: On Sun, Sep 21, 2003 at 01:07:15AM -0400, Daniel Eischen wrote:
: > But you seem to thing -pthread == NOOP unbreaks ports ;-)
:
: Warner might
It appreas to unbreak one port: icecast. It was the first port I
found so I assumed many ports were that way, but I couldn't find any
others having gone and looked at the breakage right now.
: but Kris doesn't. Kris is asking for the -pthread option
: to be restored to let -current users breath easy while the task of updating
: the ports goes on. Then he's happy for it to become a noop.
I'd be cool with this. I don't think the 'unfreeze the ports' option
is a viable one, which leaves us with this.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030920.235723.32536816.imp>