On Thu, Mar 06, 2003 at 08:44:13PM -0300, Norberto Bensa wrote:
Hmm, you're doing it the hard way, no doubts :-)
# ACCEPT_KEYWORDS=~x86 emerge whateverpackage
This is what I do. However, whenever I later do a
emerge -u world, my whateverpackage will be downgraded to the old
version.
I'm
On Sat, 8 Mar 2003 18:30:20 +0100
Fredrik Jagenheim [EMAIL PROTECTED] wrote:
I think you can do emerge -uU world, -U flag should prevent unstable ebuilds
which were emerged with ACCEPT_KEYWORDS=~x86.
At least it works for me, im using nvidia 4xxx ebuilds which are normally
masked. But with -U
If I install some ebuilds from the unstable/testing group using
ACCEPT_KEYWORDS=~x86 can I then go back and remove the
accept_keywords setting and install the stable package builds or will
this cause a problem? If this is a problem, will I be able to install
older ebuilds (say apache 1.3.27
What's the difference between the two?
Jason
Louis C. Candell wrote:
Jason Giangrande [EMAIL PROTECTED] writes:
If I install some ebuilds from the unstable/testing group using
ACCEPT_KEYWORDS=~x86 can I then go back and remove the
accept_keywords setting and install the stable package
Jason Giangrande [EMAIL PROTECTED] writes:
What's the difference between the two?
One of them ( the one I suggested ) lets you unmask individual ebuilds as opposed to
ACCEPT_KEY... which unmasks everything which is masked. Be warned, some
ebuilds will not work without some tweaking, so do not
On Thursday 06 March 2003 08:08 pm, Louis C. Candell wrote:
Jason Giangrande [EMAIL PROTECTED] writes:
What's the difference between the two?
One of them ( the one I suggested ) lets you unmask individual ebuilds as
opposed to ACCEPT_KEY... which unmasks everything which is masked.
Hmm,
