From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug
Date: Mon, 07 Dec 2009 05:18:27 -0600 [thread overview]
Message-ID: <4B1CE483.2090006@gmail.com> (raw)
In-Reply-To: <20091207104852.042d2a36@digimed.co.uk>
Neil Bothwick wrote:
> On Sat, 05 Dec 2009 19:15:29 -0600, Dale wrote:
>
>
>>>> Good catch Volker. I didn't notice that part. He needs to become
>>>> very familiar with the -1 option but even that is not good in every
>>>> case. If it is a package that needs to be in world, then that option
>>>> shouldn't be used either otherwise a --depclean would remove it.
>>>>
>
>
>>> He's updating, so packages that need to be in world are already there.
>>>
>
>
>> If he is using the command he typed in, his world file is going to be
>> huge. Read what he wrote again. He is doing the updates individually
>> without a -u or a -1 or anything else. That means every time he
>> updates, that package goes into the world file.
>>
>
> I read, and understood, what he wrote, even if it turned out to be not
> wheat he meant. I was responding to your "If it is a package that needs
> to be in world, then that option shouldn't be used either otherwise a
> --depclean would remove it." which is not true if the package is already
> in world.
>
I was making the point tho that if it is a new emerge and needs to be in
world, then the -1 option would not add it. If a person them runs
--depclean, it would them remove the package and its dependencies. I
know for me at least, I rarely re-emerge the same package twice by
hand. If I change the USE flags, I let -n catch that. If it is a
update, I let -u catch that.
Dale
:-) :-)
next prev parent reply other threads:[~2009-12-07 12:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-01 16:02 [gentoo-user] Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug Nikos Chantziaras
2009-12-02 10:51 ` Alan McKinnon
2009-12-02 13:45 ` [gentoo-user] " Nikos Chantziaras
2009-12-02 14:18 ` Neil Bothwick
2009-12-02 16:11 ` Volker Armin Hemmann
2009-12-02 14:33 ` Kevin O'Gorman
2009-12-02 14:48 ` Philip Webb
2009-12-02 15:30 ` Alan McKinnon
2009-12-02 15:49 ` Jesús Guerrero
2009-12-02 17:59 ` Stefan G. Weichinger
2009-12-02 20:04 ` Alan McKinnon
2009-12-02 20:54 ` Stefan G. Weichinger
2009-12-02 16:12 ` Nikos Chantziaras
2009-12-02 16:21 ` Neil Bothwick
2009-12-02 16:46 ` felix
2009-12-04 23:02 ` daid kahl
2009-12-05 5:14 ` Philip Webb
2009-12-05 6:47 ` Dale
2009-12-05 13:31 ` Volker Armin Hemmann
2009-12-05 14:10 ` Dale
2009-12-05 17:24 ` Neil Bothwick
2009-12-06 1:15 ` Dale
2009-12-06 2:21 ` Philip Webb
2009-12-06 2:53 ` daid kahl
2009-12-06 9:06 ` Dale
2009-12-07 10:46 ` Neil Bothwick
2009-12-07 10:48 ` Neil Bothwick
2009-12-07 11:18 ` Dale [this message]
2009-12-05 15:08 ` Neil Bothwick
2009-12-05 16:10 ` Volker Armin Hemmann
2009-12-05 19:09 ` Philip Webb
2009-12-05 20:14 ` Volker Armin Hemmann
2009-12-06 6:20 ` Alan McKinnon
2009-12-06 6:19 ` Alan McKinnon
2009-12-06 19:49 ` Philip Webb
2009-12-07 11:01 ` Neil Bothwick
2009-12-07 22:46 ` Philip Webb
2009-12-07 23:04 ` Alan McKinnon
2009-12-08 0:17 ` Dale
2009-12-08 11:19 ` Arttu V.
2009-12-08 1:04 ` Neil Bothwick
2009-12-05 16:05 ` daid kahl
2009-12-05 16:26 ` [gentoo-user] Re: Heads up: Your system might be broken and/or insecure due to serious patch-2.6 bug, " Peter Humphrey
2009-12-06 10:59 ` Peter Humphrey
2009-12-06 14:11 ` Volker Armin Hemmann
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=4B1CE483.2090006@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