Received: from spf5.us4.outblaze.com (spf5.us4.outblaze.com [205.158.62.27]) by sdf.lonestar.org (8.13.1/8.12.10) with ESMTP id j173hP6L027305 for ; Mon, 7 Feb 2005 03:43:25 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf5.us4.outblaze.com (Postfix) with ESMTP id 9A2A476FB4 for ; Mon, 7 Feb 2005 03:44:17 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cy01p-00031b-Nn for migo@homemail.com; Sun, 06 Feb 2005 22:57:37 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Cy00s-0002jl-8r for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 22:56:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Cy00k-0002fY-4H for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 22:56:31 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Cy00j-0002dN-Ht for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 22:56:29 -0500 Received: from [203.22.251.250] (helo=mg1.works.net.au) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1CxzV4-0007b6-7D for gnu-arch-users@gnu.org; Sun, 06 Feb 2005 22:23:46 -0500 Received: from aardvark.ozdial.net.au (aardvark.ozdial.net.au [203.22.251.121]) by mg1.works.net.au (8.12.11/linuxconf) with ESMTP id j173OC5f029578; Mon, 7 Feb 2005 14:24:12 +1100 Received: from lifelesswks.robertcollins.net (dsl-79.14.240.220.rns02-kent-syd.dsl.comindico.com.au [220.240.14.79]) by aardvark.ozdial.net.au (8.12.8/linuxconf) with ESMTP id j173NHoG001581; Mon, 7 Feb 2005 14:23:19 +1100 Received: from [3ffe:8002:1004:0:290:f5ff:fe23:434] (helo=lifelesslap.robertcollins.net ident=Debian-exim) by lifelesswks.robertcollins.net with asmtp (Exim 4.34) id 1CxzUb-0001Yw-Ib; Mon, 07 Feb 2005 14:23:17 +1100 Received: from localhost ([127.0.0.1] ident=robertc) by lifelesslap.robertcollins.net with esmtp (Exim 4.34) id 1CxzTt-0004vA-TU; Mon, 07 Feb 2005 14:22:33 +1100 Subject: Re: [Gnu-arch-users] GNU Arch status update From: Robert Collins To: Tom Lord In-Reply-To: <200502070259.SAA06915@emf.net> References: <200502070259.SAA06915@emf.net> Date: Mon, 07 Feb 2005 14:22:33 +1100 Message-Id: <1107746553.11080.27.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.3.2 X-MG1-Works-MailScanner-Information: Please contact the ISP for more information X-MG1-Works-MailScanner: Found to be clean X-MG1-Works-MailScanner-SpamCheck: not spam, SpamAssassin (score=-2.599, required 5, autolearn=not spam, BAYES_00 -2.60) X-MailScanner-From: rbcollins@cygwin.com Cc: gnu-arch-users@gnu.org, ben@benfinney.id.au X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1862767437==" Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 4122 Lines: 114 --===============1862767437== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-G4zsax27d1cHAX0Mz0Tj" --=-G4zsax27d1cHAX0Mz0Tj Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-02-06 at 18:59 -0800, Tom Lord wrote: >=20 >=20 > From: Ben Finney >=20 > The roadmap says: >=20 > "GNU Arch 1.3.1 15 Mar 2005 -- This will be primarily a > maintenance/rejuvination release of GNU Arch 1.x. Experience has > shown that permitting the baz line to serve as the de facto mainli= ne > for GNU Arch 1.x will be highly problematic." >=20 > For those who came in late, can someone point to these experiences > (blog entries? mailing list thread URL?) showing that following > baz will be "highly problematic" for GNU Arch? >=20 > >From my perspective, 1.4pre1 has some serious regressions. For example, > it does not build at all on one of my boxes (on which earlier releases > had no problem) and, once tweaked to build, fails `make test'. > The box in question is an exceptionally clean, robust, and rich Posix > compatible environment hence my labling this regression "serious". Some details would help be here. For example, if the failure is removing libneons bundling, thats one thing. If the build failure is something else, something that came from baz, I'd love to know about it - then I could fix it.=20 Likewise the test case failures are very concerning for me. So what, pray tell is the regression ?. > In the pipeline (I am told) are baz changes that will make that > even worse (e.g., a deliberate hard dependency on GNU libc). Erm, the only one I know of is the discussion about using the system regex library rather than the hackerlab one - and that only if we can't easily fix :cut: in hackerlab. I'm not aware of any hard dependencies planned on GNU libc - as native windows support is a major goal, that would be pretty darn silly. Where did you get that information ? (I'd like to correct it at the source if I can). > Basically, in spite of good efforts all around, on both branches, 1.4pre1 > falls way short of my quality expectations and goals and the expense of > directly trying to fix it from its current state looks quite daunting > to me. Don't be confused about that though: my judgement re 1.4pre1 > doesn't necessarily imply anything at all about whether or not baz itself > is doing a good job of achieving the goals for which that branch was=20 > created. >=20 > Finally, I should point out that the 1.4 series isn't being killed or > even direction-shifted. It's still there. Should my judgement prove > wrong, and coasting on Baz's wake again appear the right thing for GNU > Arch to do, the option is still open. Meanwhile, the 1.3.X series is > a context in which to take a more proactive approach to GNU Arch > (including, presumably, merging at least /some/ changes from baz). Cool. > Does that clarify things a bit? People often complain that I seem to > always express myself with a "negative tone". That's certainly not my > intent here. 1.4pre1 was a valuable experiment, in my book, and the > final chapter on merging from baz to GNU Arch is far from written. Certainly it clarifies things for me, my incipient flame-bait has been erased ... Rob --=-G4zsax27d1cHAX0Mz0Tj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBCBt75M4BfeEKYx2ERAsEdAKCXOYKkgnUnazui2b8lkdjHMUF4ywCfW2ow sABBwfKY/thvMr4WvWuTkZo= =XBpT -----END PGP SIGNATURE----- --=-G4zsax27d1cHAX0Mz0Tj-- --===============1862767437== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ --===============1862767437==--