From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29203 invoked from network); 2 May 2004 20:02:51 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 2 May 2004 20:02:51 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BKNAp-0005hX-57 for arch-gentoo-dev@lists.gentoo.org; Sun, 02 May 2004 20:02:51 +0000 Received: (qmail 26455 invoked by uid 50004); 2 May 2004 20:02:50 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 3965 invoked from network); 2 May 2004 20:02:50 +0000 From: Paul de Vrieze To: gentoo-dev@lists.gentoo.org Date: Sun, 2 May 2004 22:02:27 +0200 User-Agent: KMail/1.6 References: <1083296558.8842.127.camel@woot.uberdavis.com> <1083517271.28139.23.camel@localhost> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_iPVlAkKGP3zACPH"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200405022202.42639.pauldv@gentoo.org> Subject: Re: [gentoo-dev] 2004.2 Feature Requests X-Archives-Salt: 70238cfc-13bb-4391-9d1c-8c983125e478 X-Archives-Hash: 24fff50f271d8e2c42e9aac011c13ebe --Boundary-02=_iPVlAkKGP3zACPH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 02 May 2004 21:34, Pieter Van den Abeele wrote: > I noted that projects whose requirements indicate they will be (amongst > other architectures) ppc compatible, but are implemented and designed > by people without much ppc expertise and whose lead hasn't proactively > involved people with ppc expertise, at least for testing (assuming > something testable is available), will require a lot of work on my part > when they suddenly become obliged (as in: a feature for all the > architectures releasing), in this case less than 2 weeks before I need > to start building the 2004.2 release. (check releng release roadmap). Maybe in general it might be an idea (also for other archs) to make a list = of=20 the most common pitfalls (and their fixes) when using that arch. To mind co= me=20 things like big or little endian, and 64 vs. 32 bits. We might even go so f= ar=20 as to write a description on how to correct broken upstream source. Paul =2D-=20 Paul de Vrieze Gentoo Developer Mail: pauldv@gentoo.org Homepage: http://www.devrieze.net --Boundary-02=_iPVlAkKGP3zACPH Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAlVPibKx5DBjWFdsRApZcAJ9VSnDBeE1we85znN/Oe5omk45qtQCfdDco ipqgNCkBYa7r41QJmQTzKQw= =/tvT -----END PGP SIGNATURE----- --Boundary-02=_iPVlAkKGP3zACPH--