From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Ruby keywording
Date: Wed, 07 Mar 2012 08:00:16 +0100 [thread overview]
Message-ID: <4F570780.2030409@gentoo.org> (raw)
In-Reply-To: <20120306221734.GO15707@schlaumatte.ethz.ch>
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]
On 3/6/12 11:17 PM, Thomas Kahle wrote:
> the x86 team has many ruby keywording bugs in the queue and it is
> hard to keep up because testing them can be a pain. There are tons
> of circular deps with USE="test" or USE="doc", there are the
> different ruby interpreters.
Yeah. Maintainers, if you get delays on arch-related bugs it's often
because of pain like this.
> Also the inter-bug dependencies are often not resolved correctly,
> that is the to be keyworded package depends on non-keyworded stuff
> not listed in the bug.
And this is even worse. Please check things with repoman before filing
bugs. You can even write automated scripts at least for the "check
whether we got all deps right" part.
> All of these packages are already keyworded ~amd64. Ruby is an
> interpreted language, I don't see any point in having every arch team
> do the testing for every small package. Could the ruby team add ~x86
> themselves after testing on ~amd64, or are there compelling reasons
> to not do this?
It's trivial to set up x86 chroot on amd64 box, so I can't imagine
what's preventing people from creating such chroot, doing the testing
and keywording themselves.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 203 bytes --]
next prev parent reply other threads:[~2012-03-07 7:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 22:17 [gentoo-dev] Ruby keywording Thomas Kahle
2012-03-06 22:42 ` Jeroen Roovers
2012-03-07 7:00 ` "Paweł Hajdan, Jr." [this message]
2012-03-07 12:25 ` Alexis Ballier
2012-03-07 14:54 ` Thomas Kahle
2012-03-07 16:09 ` Alexis Ballier
2012-03-07 18:56 ` Hans de Graaff
2012-03-07 18:52 ` Hans de Graaff
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=4F570780.2030409@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.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