Date: Sun, 21 Sep 2003 00:31:37 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Kris Kennaway <kris@obsecurity.org> Cc: h@schmalzbauer.de Subject: Re: Fixing -pthreads (Re: ports and -current) Message-ID: <1064118697.62885.4.camel@gyros> In-Reply-To: <20030921042207.GA40487@rot13.obsecurity.org> References: <20030920.164621.68039520.imp@bsdimp.com> <Pine.GSO.4.10.10309202038570.19227-100000@pcnet5.pcnet.com> <20030921022407.GA39970@rot13.obsecurity.org> <20030921040340.GC28195@freebsd1.cimlogic.com.au> <20030921042207.GA40487@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-QWB04yvqoOzv7PjMddj8 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2003-09-21 at 00:22, Kris Kennaway wrote: > On Sun, Sep 21, 2003 at 02:03:40PM +1000, John Birrell wrote: > > On Sat, Sep 20, 2003 at 07:24:07PM -0700, Kris Kennaway wrote: > > > 3) You, John Birrell, and whoever else is interested in fixing these > > > ports can work on them at your own pace without disrupting life for > > > the rest of the users. Once they're all fixed, we can turn the error > > > back on or make it a NOP or do whatever else is decided to be > > > appropriate. > >=20 > > OK, so what's the commit procedure going to be? This could generate an > > awful lot of little PRs. >=20 > Call for volunteers, take the list of failed ports from dosirak and > divide it up between yourselves, then mark off the ports as fixes are > developed. The fixes can be committed once the freeze is over (and > they are demonstrated not to break on 4.x). >=20 > There's no reason this needs to be coordinated through GNATS, and > indeed that would probably be counter-productive. Since it won't be > affecting people outside the testing group who continue to run a gcc > that treats -pthread as an error, duplicate or bogus PRs won't be > generated by people who aren't in the loop. >=20 > > Scot posted a patch for bsd.port.mk. Is that going to be committed? > > That's needed. >=20 > Sure, if it works. I can test it once the current 5.x build finishes > on dosirak. >=20 > > Are you prepared to unlock the ports tree and allow a blanket commit au= th > > for commits that only change patch-configure? That should catch most of > > the simple cases. >=20 > I'm unsure of the current status - the original schedule called for > the ports tree to be tagged yesterday, but now the schedule has > slipped. marcus is in charge of this release, so he'll have to > comment on the updated timeline. However, we need to be careful not > to destabilize 4.9 in committing hasty and poorly-tested fixes for > problems on -current that do not also work on 4.x (this is > unfortunately a common occurrence). I will most likely be tagging the tree sometime this week once things have stabilized with the recent GNOME and KDE commits. I do not want to start having -pthread commits go in at this time as they do not help the -STABLE build process. Joe >=20 > At any rate, 4.9 will be released sooner or later, and in following > step 1) of my proposal the only people the freeze will continue to > affect are those who are working on fixing the -pthread issues, which > can be kept in private repositories for a week or two. For everyone > else, ports that use -pthread will go back to working again (modulo > pre-existing compile failures). >=20 > Kris --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-QWB04yvqoOzv7PjMddj8 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD4DBQA/bSmpb2iPiv4Uz4cRAqqjAJjG8AiwtyMIM1cGVkOWm5JfXJxlAJ43oPKg FJtbTFmeSgJLVV65zMJyjg== =SV3p -----END PGP SIGNATURE----- --=-QWB04yvqoOzv7PjMddj8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1064118697.62885.4.camel>