From: Weeve <weeve@gentoo.org>
To: Gentoo Dev Mailing List <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] DEVS: depedency checking for other arches
Date: Wed, 9 Jul 2003 09:00:34 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0307090845140.31115@stargazer.weeve.org> (raw)
-----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
next reply other threads:[~2003-07-09 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 13:00 Weeve [this message]
2003-07-09 14:01 ` [gentoo-dev] DEVS: depedency checking for other arches Bartosch Pixa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0307090845140.31115@stargazer.weeve.org \
--to=weeve@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox