From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14217 invoked by uid 1002); 9 Jul 2003 13:00:40 -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 4234 invoked from network); 9 Jul 2003 13:00:40 -0000 Date: Wed, 9 Jul 2003 09:00:34 -0400 (EDT) From: Weeve X-X-Sender: gen-email@stargazer.weeve.org To: Gentoo Dev Mailing List Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: [gentoo-dev] DEVS: depedency checking for other arches X-Archives-Salt: b8125d8f-b780-4de9-a137-682782032b53 X-Archives-Hash: 37efab6af8da6160ae418a27d65a63ca -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, Just a request/plea to developers in regards to adding/adjusting dependencies on ebuilds that have multiple arch keywords (i.e. x86, ppc, sparc, mips, etc). When a dependency is added or adjusted for an existing ebuild, particularly ones that have multiple arch keywords, please please please check to see if those dependencies can be built for all other arches for the same tree the ebuild you are working on is currently marked for (stable or unstable). An example of what sometimes happens; I'm working on ebuild foo-1.0.ebuild. A bug comes in asking to fix a dependency on foo-1.0.ebuild so that it will depend on bar-1.0. Currently, foo-1.0.ebuild has keywords for x86, ppc and ~sparc. However, bar-1.0.ebuild only has keywords for x86. A dev who only has x86 to test on adds the dependency to bar-1.0 into foo-1.0.ebuild and closes out the bug. Unknowingly to that dev, he's just caused a dependency break for ppc and ~sparc because repoman isn't checking for these, only x86. I have submitted a bug for repoman to get the capability to check dependencies for arches other than the one you are currently on (#24160). In the meantime, a couple suggestions as to how to handle this; 1) When adjusting ebuilds, check to see if the dependencies have the same keywords. If not contact a dev from that arch to see if they can test those packages and get them marked similarly to the ebuild you are working on. 2) Make the new/adjusted dependencies only for the arches you can test on, and then create bugs in bugzilla asking the other arches to test the dependencies. Thanks, and reply away! :-P - -- Weeve Gentoo/Sparc Team Lead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/DBH2dKvgdVioq28RAo/EAJ9B0RkdgKF8JGioeBw4Oc6qV7lWFwCfeLmH 9BPMnXQ73LwjKGoPNPhUTI0= =vbva -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list