From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Any nice tools for emerge dependency resolution listing?
Date: Sat, 06 Mar 2010 23:30:11 -0600 [thread overview]
Message-ID: <4B9339E3.3070606@gmail.com> (raw)
In-Reply-To: <6e2210231003062101s226094baw1b39ae100d41498b@mail.gmail.com>
Mark David Dumlao wrote:
> On Sun, Mar 7, 2010 at 3:15 AM, Dale<rdalek1967@gmail.com> wrote:
>
>> I'll add this as well. If you use autounmask and you have portage.unmask
>> and friends as a directory, it names each file and does them separately.
>> So, if you use it and don't like it, just delete the file and do something
>> else.
>>
>> If you still have package.unmask and friends as a file, it separates each
>> run into the file. It tells where it starts and where it ends so it is a
>> lot easier to delete things if you don't like or want something there
>> anymore.
>>
>> It's pretty neat.
>>
> Beautiful! I'm trying it out right now... autounmask may be more
> organized than I ever was if I just keep targetting meta packages and
> manually unblocking key blockers.
>
> Anyone else have neat package.*/ organization tricks I haven't heard of?
>
>
>> Dale
>>
>> :-) :-)
>>
>>
>>
The only thing I have noticed, it doesn't seem to work with layman. It
may be a setting on my part or it just doesn't see them but I can't get
it to work with layman stuff. I been trying to figure out the newer KDE
4 stuff. Google is getting tired of me. lol
Dale
:-) :-)
prev parent reply other threads:[~2010-03-07 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 10:19 [gentoo-user] Any nice tools for emerge dependency resolution listing? Mark David Dumlao
2010-03-06 11:45 ` Mick
2010-03-06 11:46 ` Alan McKinnon
2010-03-06 11:53 ` Daniel Wagener
2010-03-06 14:10 ` Mark David Dumlao
2010-03-06 19:15 ` Dale
2010-03-07 5:01 ` Mark David Dumlao
2010-03-07 5:30 ` Dale [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=4B9339E3.3070606@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