Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-alt
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-alt@g.o
From: heroxbd@...
Subject: Re: Best Practice in Adopting New Ebuilds in Prefix
Date: Sat, 06 Aug 2011 09:13:00 +0900
Dear Zac, 

Zac Medico <zmedico@g.o> 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?

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.

> Also, it's common to use emerge's --autounmask-write option to
> populate this file automatically.

O, I would give it a try.

Regards,
Benda

1. http://www.gentoo.org/proj/en/glep/glep-0022.html

-- 
XU Benda
Research Center for Neutrino Science
Tohoku University
JAPAN

http://www.awa.tohoku.ac.jp/~benda


Replies:
Re: Best Practice in Adopting New Ebuilds in Prefix
-- Zac Medico
References:
Best Practice in Adopting New Ebuilds in Prefix
-- heroxbd
Re: Best Practice in Adopting New Ebuilds in Prefix
-- Zac Medico
Navigation:
Lists: gentoo-alt: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Best Practice in Adopting New Ebuilds in Prefix
Next by thread:
Re: Best Practice in Adopting New Ebuilds in Prefix
Previous by date:
Re: Best Practice in Adopting New Ebuilds in Prefix
Next by date:
Re: Best Practice in Adopting New Ebuilds in Prefix


Updated Jun 18, 2012

Summary: Archive of the gentoo-alt mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.