public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Portage problem with xfce4-panel
Date: Wed, 28 Feb 2007 00:00:41 -0500	[thread overview]
Message-ID: <yu9ejoa511i.fsf@nyu.edu> (raw)
In-Reply-To: <33a557360702272043s3df63dbct113ce1b715984dfb@mail.gmail.com> (Bruno Espinoza's message of "Tue\, 27 Feb 2007 23\:43\:30 -0500")

At Tue, 27 Feb 2007 23:43:30 -0500 Bruno Espinoza <bruno32@gmail.com> wrote:

> Exist a much easier way to avoid unmasking packages. Go to your
> /etc/make.conf. Change your architecture from "x86" to "~x86". Now emerge
> xfce4-panel. If you don't want to be in the testing architecture. Go back
> and change "~x86" to "x86". That's pretty easy... and no need to unamsk!

I would worry that the emerge of xfce4-panel might then bring in other
testing packages as dependencies (but I don't know for sure).

I would think it saver to add xfce-panel to package.keywords

    echo xfce-extra/xfce4-panelmenu >> /etc/portage/package.keywords

(mkdir /etc/portage    if you don't already have it.)

There are various prefixes and suffixes you could add.
See    man portage     for details

For example my package.keywords is currently

x11-misc/googleearth
app-editors/emacs-cvs
~x11-drivers/nvidia-drivers-1.0.8774
~net-print/cups-1.2.1-r2
~app-text/libpaper-1.1.14.8
net-wireless/bcm43xx-fwcutter
#~media-gfx/graphviz-2.12

allan


-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2007-02-28  5:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 16:38 [gentoo-user] Portage problem with xfce4-panel Grant
2007-02-27 19:47 ` Bo Ørsted Andresen
2007-02-28  0:07   ` Grant
2007-02-28  4:43     ` Bruno Espinoza
2007-02-28  5:00       ` Allan Gottlieb [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=yu9ejoa511i.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --cc=gentoo-user@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