From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Where has package.keywords gone?
Date: Thu, 29 Mar 2007 20:02:36 +0200 [thread overview]
Message-ID: <20070329200236.551230b4@c1358217.kevquinn.com> (raw)
In-Reply-To: <200703291732.01608.prh@gotadsl.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Thu, 29 Mar 2007 17:32:01 +0100
Peter Humphrey <prh@gotadsl.co.uk> wrote:
> I used to have a package.keywords file in /etc/portage/, but since
> installing crossdev that is now a directory, thus:
>
> # ls -l /etc/portage/package.keywords
> total 4
> -rw-r--r-- 1 root root 202 2007-02-11 10:52 cross-i686-pc-linux-gnu
Hmm; crossdev shouldn't have deleted the file - if you're confident
that's what did it, file a bug on bugzilla.gentoo.org against
crossdev. Include the exact version of crossdev that you have.
Normally crossdev would append its data to the file, if it was
previously a file, and if it was a directory (or didn't exist, I guess)
crossdev would put its data in a file in the directory (as you see
above).
> Now where has the old file gone, and where do I put things that I
> would have put in it? The portage Web page offers no hints.
I would imagine that the old file has been deleted. You can put the
data in any filename inside (what is now the
directory) /etc/portage/package.keywords/ You can call the file
whatever you want - indeed you can have as many files as you want, so
you can group the keyworded packages in a way that's suitable for you.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-29 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 16:32 [gentoo-amd64] Where has package.keywords gone? Peter Humphrey
2007-03-29 18:02 ` Kevin F. Quinn [this message]
2007-03-30 15:37 ` Peter Humphrey
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=20070329200236.551230b4@c1358217.kevquinn.com \
--to=kevquinn@gentoo.org \
--cc=gentoo-amd64@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