From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: package.keywords
Date: Tue, 23 Jun 2009 01:51:45 -0500 [thread overview]
Message-ID: <4A407B81.7060702@gmail.com> (raw)
In-Reply-To: <200906230842.12270.alan.mckinnon@gmail.com>
Alan McKinnon wrote:
> On Tuesday 23 June 2009 01:17:16 Dale wrote:
>
>> Neil Bothwick wrote:
>>
>>> On Mon, 22 Jun 2009 15:51:31 +0000 (UTC), James wrote:
>>>
>>>> I'm mostly running stable with exceptions being enabled
>>>> via the /etc/portage file structure. Usually it's small,
>>>> but now with kde4, BLOAT is my modus operandi,
>>>> not by choice......
>>>>
>>> It's easier to manage if you make portage.keywords a directory then put
>>> the actual packages in files within that directory. That way you can
>>> separate the files needed to run KDE4 from any other group of packages.
>>>
>>> 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? Say, one named KDE4 to put
>> all of KDE4 and it's little friends and then another for some other set
>> of packages? Is this sort of like the sets thing which I am still
>> curious about?
>>
>
> Yes, precisely.
>
> If package.keywords is a single file, then all your keywords must be in that
> file. This is difficult for ebuilds to manipulate, and difficult for you to
> edit too. If I send you my list of KDE keywords, you have to copy paste the
> lot into a file and put comments at the start and end so you know what it all
> is.
>
> If package.keywords is a directory, then portage/ebuilds/tools/you can add and
> remove entire files easily, leaving everything else untouched.
>
>
>> Right now, package.keywords and friends are files not directories.
>> Maybe tarring up your portage directory and emailing me off list would
>> help? I need a light bulb moment here. :/
>>
>
> It's easy. As root:
>
> cd /etc/portage
> mv package.keywords package.keywords~
> mkdir package.keywords
> mv package.keywords~ package.keywords/package.keywords
>
> The destination file in the last command can be named anything you like.
>
> Now, if you install enlightenment, create and edit
> /etc/portage/package.keywords/e17
> If I send you my KDE keywords as an attachment, right-click, Save As,
> /etc/portage/package.keywords/kde4
>
> Done, sorted.
>
>
This sounds cool. I don't unmask a lot or anything but something like
KDE 4 comes to mind for this. That requires a lot of work. I'm going
to have to check to see if autounmask supports this too.
Thanks much. Light bulb is glowing a bit now. o_O
Dale
:-) :-)
next prev parent reply other threads:[~2009-06-23 6:52 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
2009-06-23 6:42 ` Alan McKinnon
2009-06-23 6:51 ` Dale [this message]
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=4A407B81.7060702@gmail.com \
--to=rdalek1967@gmail.com \
--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