From: Zac Medico <zmedico@gentoo.org>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] Best Practice in Adopting New Ebuilds in Prefix
Date: Fri, 05 Aug 2011 17:42:29 -0700 [thread overview]
Message-ID: <4E3C8DF5.8090602@gentoo.org> (raw)
In-Reply-To: <86ei0zwg6r.fsf@gmail.com>
On 08/05/2011 05:13 PM, heroxbd@gmail.com wrote:
> Dear Zac,
>
> Zac Medico <zmedico@gentoo.org> writes:
>
>> This is totally unnecessary, since you can use
>> $EPREFIX/etc/portage/package.accept_keywords for these.
>
> Ah-ha, from GLEP22[1], e.g. ~amd64 is a default to ~amd64-linux. Why
> don't we just treat these reasonable defauls as equal in the portage?
You can configure that yourself by setting ACCEPT_KEYWORDS="~amd64
amd64" in make.conf.
However, it's not generally recommended since when ~amd64-linux is
missing from KEYWORDS it means that it may not have been tested in a
amd64-linux prefix environment. Sometimes it will work, but it's also
common for such ebuilds to try and install files outside of $EPREFIX
which will cause them to abort before they are installed.
Also, if you use package.accept_keywords along with --autounmask-write,
then you'll have a list of packages that is convenient if you plan to
submit keyword requests.
> I see bugs (and submit myself) in bugzilla to add keywords as
> ~amd64-linux when there is already ~amd64. Wondering the motivation of
> doing it explicitly.
In order to indicate that it has been tested in a prefix environment,
versus a non-prefix environment.
--
Thanks,
Zac
next prev parent reply other threads:[~2011-08-06 0:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 1:36 [gentoo-alt] Best Practice in Adopting New Ebuilds in Prefix heroxbd
2011-08-03 5:49 ` Zac Medico
2011-08-06 0:13 ` heroxbd
2011-08-06 0:42 ` Zac Medico [this message]
2011-08-06 1:24 ` heroxbd
2011-08-03 8:07 ` Fabian Groffen
2011-08-06 1:05 ` heroxbd
2011-08-06 7:37 ` Fabian Groffen
2011-08-10 1:17 ` heroxbd
2011-08-10 6:44 ` Fabian Groffen
2011-08-05 20:00 ` Jeremy Olexa
2011-08-10 1:31 ` heroxbd
2011-08-10 4:42 ` Jeremy Olexa
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=4E3C8DF5.8090602@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-alt@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