From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Merging or overwriting KEYWORDS from eclass
Date: Tue, 24 Jun 2008 21:32:13 +0400 [thread overview]
Message-ID: <1214328733.3331.13.camel@camobap> (raw)
In-Reply-To: <200806240153.58516.rbu@gentoo.org>
В Втр, 24/06/2008 в 01:53 +0200, Robert Buchholz пишет:
> I've stumbled upon an inconsitency between package managers the other
> day [1], which was due to both an ebuild and an eclass defining
> inconsisting KEYWORDS.
But do we allow KEYWORDS in eclasses? Why? Each package should be tested
independently on each arch and there is no sane way to test all ebuilds
that inherit eclass... Or do we have exceptions? If so, then ebuilds for
dictionaries and stardict.eclass could be perfect exception, but QA team
prohibited usage of KEYWORDS in stadict eclass. See bug 163833 .
--
Peter.
--
gentoo-dev@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-06-24 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 23:53 [gentoo-dev] Merging or overwriting KEYWORDS from eclass Robert Buchholz
2008-06-23 23:55 ` Brian Harring
2008-06-24 10:05 ` [gentoo-dev] " Tiziano Müller
2008-06-24 15:29 ` Brian Harring
2008-06-24 17:32 ` Peter Volkov [this message]
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=1214328733.3331.13.camel@camobap \
--to=pva@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