From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: package.keywords
Date: Tue, 23 Jun 2009 00:45:08 +0100 [thread overview]
Message-ID: <20090623004508.2cf1d7a2@zaphod.digimed.co.uk> (raw)
In-Reply-To: <4A4010FC.5050609@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
On Mon, 22 Jun 2009 18:17:16 -0500, Dale wrote:
> > All package.* files in /etc/portage can be replaced a directories,
> > then all the files in that directory are considered as a whole.
> For some reason, my light bulb has still not came on so here comes some
> questions. I would create /etc/portage/package.keywords then inside
> that another directory or a set of files?
A set of files.
> Say, one named KDE4 to put
> all of KDE4 and it's little friends and then another for some other set
> of packages?
Exactly. The portage man page explains it well.
/etc/portage/
Any file in this directory that begins with "package." can be more than
just a flat file. If it is a directory, then all the files in that
directory will be sorted in ascending alphabetical order by file name
and summed together as if it were a single file.
Example:
/etc/portage/package.keywords/common
/etc/portage/package.keywords/e17
/etc/portage/package.keywords/kde
> Is this sort of like the sets thing which I am still
> curious about?
Not really, it's just an alternative way of organising the package.* data.
--
Neil Bothwick
Asking whether machines can think is like asking whether submarines can
swim.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-22 23:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 13:58 [gentoo-user] package.keywords James
2009-06-22 14:08 ` Albert Hopkins
2009-06-22 14:18 ` [gentoo-user] package.keywords James
2009-06-22 15:14 ` Arttu V.
2009-06-22 15:51 ` James
2009-06-22 20:28 ` Alan McKinnon
2009-06-23 14:40 ` James
2009-06-23 14:54 ` Nikos Chantziaras
2009-06-23 15:28 ` James
2009-06-23 15:40 ` Nikos Chantziaras
2009-06-23 16:09 ` [gentoo-user] ReSOLVED: package.keywords James
2009-06-23 18:42 ` Alan McKinnon
2009-06-23 14:55 ` [gentoo-user] package.keywords Neil Bothwick
2009-06-23 15:36 ` James
2009-06-23 15:05 ` Alan McKinnon
2009-06-23 15:49 ` James
2009-06-23 18:39 ` Alan McKinnon
2009-06-22 22:17 ` Neil Bothwick
2009-06-22 23:17 ` Dale
2009-06-22 23:45 ` Neil Bothwick [this message]
2009-06-23 6:42 ` Alan McKinnon
2009-06-23 6:51 ` Dale
2009-06-23 7:33 ` Neil Bothwick
2009-06-23 7:38 ` Dale
2009-06-23 8:27 ` Alan McKinnon
2009-06-23 9:16 ` Weitao Sun
2009-06-23 9:18 ` Dale
2009-06-23 10:16 ` Neil Bothwick
2009-06-23 10:51 ` Arttu V.
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=20090623004508.2cf1d7a2@zaphod.digimed.co.uk \
--to=neil@digimed.co.uk \
--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