public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Aust <christian@wilde-welt.de>
To: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Missing feature for
Date: 09 Jun 2003 23:52:01 +0200	[thread overview]
Message-ID: <1055195521.16083.5.camel@localhost> (raw)
In-Reply-To: <20030609232840.19d6eed5.daniel.armyr@home.se>

Am Mo, 2003-06-09 um 23.28 schrieb Daniel Armyr:
> Have you looked into the PORTAGE_OVERLAY setting in /etc/make.conf. It is my experience that an ebuild with the same version in the overlay dir will override the one in /usr/portage. So when I want to use an unstable package, I copy it to the overlay, and edit the KEYWORDS variable in the ebuild. A bit hacky, but it works.
> --Daniel Armyr

In gentoo forums I've found this:

If you are using Portage >= 2.0.48, there is another option for
installing masked packages that does not require editing package.mask.
You can add a category/package entry into the file
/etc/portage/package.unmask, which will survive across an "emerge sync".

[http://forums.gentoo.org/viewtopic.php?t=33534]

I've tried it, but it didn't show any effect. Currently this file just
consists of 

sys-devel/gcc-3.3

What else should be in there? Will this file be loaded every time I
emerge something, or do I have to regen something? Best regards,

-  Christian

-- 

Christian Aust
mailto:christian@wilde-welt.de
icq: 84500990 - Yahoo!: datenimperator - MSN: datenimperator
GPG: 3C89AD72



--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-06-09 21:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 20:56 [gentoo-dev] Missing feature for Christian Aust
2003-06-09 21:28 ` Daniel Armyr
2003-06-09 21:52   ` Christian Aust [this message]
2003-06-09 22:05     ` Marius Mauch
2003-06-09 22:08 ` Kumba
2003-06-10  8:21 ` [gentoo-dev] not missing feature for package.unmask Stanislav Brabec
2003-06-11  0:02   ` Kurt V. Hindenburg
2003-06-11 13:08     ` Alastair Tse
2003-06-11 14:21       ` Kurt V. Hindenburg

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=1055195521.16083.5.camel@localhost \
    --to=christian@wilde-welt.de \
    --cc=gentoo-dev@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