public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Darren Kirby <bulliver@badcomputer.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] how thorough is #emerge --sync?
Date: Wed, 18 Oct 2006 14:35:26 -0700	[thread overview]
Message-ID: <200610181435.26211.bulliver@badcomputer.org> (raw)
In-Reply-To: <20061018210202.28937.qmail@web31710.mail.mud.yahoo.com>

Quoth the maxim wexler
> > # echo "media-sound/dir2ogg ~x86" >>
> > /etc/portage/package.keywords
> >
> > and that will install dir2ogg-0.9.1.
>
> Not yet. There's gotta be more to it than that.
>
> I ran the above command then did #emerge -C dir2ogg
> then #emerge -pv dir2ogg:
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild  N    ] media-sound/dir2ogg-0.8  0 kB
>
> >From man make.conf there is this, the only mention of
>
> /etc/portage:
>
> suidctl
>     Before merging packages to the live filesystem,
> automatically strip setuid bits from any file that is
> not listed in /etc/portage/suidctl.conf.
>
> So, if portage is supposed to read package.keywords I
> don't know where the link would be made.

It is built into 'emerge' AFAIK...

You have made a typo or some other mistake. It is documented in the portage 
guide: 
http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=3#doc_chap2

Again, ensure that you have the line:

media-sound/dir2ogg ~x86

in "/etc/portage/package.keywords"

Note that this assumes you are running "x86" ARCH. If you are using a 
different arch then do the same thing but change the arch to what you are 
using: ie: "~sparc", "~ppc", or "~amd64".

-d
-- 
darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
"...the number of UNIX installations has grown to 10, with more expected..."
- Dennis Ritchie and Ken Thompson, June 1972
-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-10-18 21:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-18  3:37 [gentoo-user] how thorough is #emerge --sync? maxim wexler
2006-10-18  3:43 ` maxim wexler
2006-10-18  5:30   ` [gentoo-user] " Alexander Skwar
2006-10-18  5:53     ` Darren Kirby
2006-10-18  6:11       ` Iain Buchanan
2006-10-18  6:31       ` [gentoo-user] " Alexander Skwar
2006-10-18 18:30         ` Darren Kirby
2006-10-18 18:57           ` Willie Wong
2006-10-18 19:20             ` Darren Kirby
2006-10-18 21:37               ` [gentoo-user] " Alexander Skwar
2006-10-18 21:31             ` Alexander Skwar
     [not found]               ` <200610181449.12060.bulliver@badcomputer.org>
2006-10-19 10:04                 ` [gentoo-user] " Alexander Skwar
2006-10-19 14:38                   ` Devon Miller
2006-10-19 14:53                     ` [gentoo-user] " Alexander Skwar
2006-10-19 17:21                     ` [gentoo-user] Re: Re: " Willie Wong
2006-10-19 19:37                     ` [gentoo-user] " Darren Kirby
     [not found]                   ` <200610191217.17509.bulliver@badcomputer.org>
2006-10-19 21:16                     ` [gentoo-user] [OT] " Justin Findlay
2006-10-18 21:27           ` [gentoo-user] Re: Re: " Alexander Skwar
2006-10-18  7:56       ` [gentoo-user] " Neil Bothwick
2006-10-18 18:23         ` Darren Kirby
2006-10-18 21:38           ` [gentoo-user] " Alexander Skwar
2006-10-18  3:44 ` [gentoo-user] " Brett I. Holcomb
2006-10-18  3:46 ` Brett I. Holcomb
2006-10-18  3:56 ` Drew
2006-10-18  4:00 ` Darren Kirby
2006-10-18 21:02   ` maxim wexler
2006-10-18 21:35     ` Darren Kirby [this message]
2006-10-19  0:06       ` maxim wexler
2006-10-19 10:09       ` Bo Ørsted Andresen
2006-10-19 18:23         ` Darren Kirby
2006-10-19 20:49           ` Daniel Barkalow
2006-10-18 21:49     ` Daniel Barkalow
2006-10-18 21:50     ` Neil Bothwick
2006-10-19  0:21     ` b.n.
2006-10-18  5:29 ` [gentoo-user] " Alexander Skwar
2006-10-18  8:01 ` [gentoo-user] " Neil Bothwick
  -- strict thread matches above, loose matches on Subject: below --
2006-10-19 14:35 Eric Bohn
2006-10-19 14:57 ` Neil Bothwick

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=200610181435.26211.bulliver@badcomputer.org \
    --to=bulliver@badcomputer.org \
    --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