From: Mark David Dumlao <madumlao@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Showing installed packages that aren't in portage tree(s)
Date: Sat, 27 Feb 2010 15:54:02 +0800 [thread overview]
Message-ID: <6e2210231002262354k67a0398cv749cf9e81994d9b9@mail.gmail.com> (raw)
In-Reply-To: <4B88B974.4090106@gmail.com>
On Sat, Feb 27, 2010 at 2:19 PM, Dale <rdalek1967@gmail.com> wrote:
> chrome://messenger/locale/messengercompose/composeMsgs.properties:
>>
>> Just what I needed. Thanks!
>>
>>
>
> Let me also add that the output has changed. I tried to clean up some
> package.* files a while back and it turned into a mess. Before you change a
> file, make a backup just in case. It seems to list some things that maybe
> it shouldn't. Maybe I am missing something somewhere but it isn't the way
> it used to be. I need to run it and just sit and study the list and test
> some things. There may be some rhyme or reason for what it is doing that I
> just don't see yet
Fear not, the redundant / missing flags in my package.xxx files are
more of an out-of-sight, out-of-mind thing for me. I figure they're
not breaking anything nor adding that much cruft by just being there.
Crufty packages though, bug me, especially when they block my
upgrades/revdeps/uninstalls.
--
This email is: [ ] actionable [ ] fyi [x] social
Response needed: [ ] yes [ ] up to you [x] no
Time-sensitive: [ ] immediate [ ] soon [x] none
next prev parent reply other threads:[~2010-02-27 7:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 3:44 [gentoo-user] Showing installed packages that aren't in portage tree(s) Mark David Dumlao
2010-02-27 3:51 ` Dale
2010-02-27 5:20 ` Mark David Dumlao
2010-02-27 6:19 ` Dale
2010-02-27 7:54 ` Mark David Dumlao [this message]
2010-02-27 17:14 ` Dale
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=6e2210231002262354k67a0398cv749cf9e81994d9b9@mail.gmail.com \
--to=madumlao@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