From: Mike Kazantsev <mike_kazantsev@fraggod.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installing outside of Portage & cruft removal
Date: Mon, 26 Jan 2009 22:57:13 +0500 [thread overview]
Message-ID: <20090126225713.1df20509@coercion> (raw)
In-Reply-To: <49bf44f10901260935y7e46b94te283d854a89269a5@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
On Mon, 26 Jan 2009 09:35:13 -0800
Grant <emailgrant@gmail.com> wrote:
> I suppose you and Jesus are right, but what about cruft removal? Are
> you saying Gentoo is 100% cruft-free? I've got a lot of junk in /etc
> and especially ~/.*
Oh, that's not a bug, it's a feature (C) some_unknown_company
AFAIK portage won't remove any changed (by hand) files in
CONFIG_PROTECT paths, and I've certainly can't remember a package,
which installs anything into ~.
Of course, if you'll launch installed app it'll create some config,
temp files, etc, but that'll only affect the paths to which it has
access, and that's probably only your ~ and /tmp.
And as soon as portage will start to "clean up" your home from
app-created files like, say, some documents you've spent weeks working
on, it'll certainly make it to the top-10 evil linux viruses out there.
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-01-26 17:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 16:41 [gentoo-user] Installing outside of Portage & cruft removal Grant
2009-01-26 16:48 ` Mike Kazantsev
2009-01-26 17:08 ` Jesús Guerrero
2009-01-30 18:45 ` b.n.
2009-01-26 17:35 ` Grant
2009-01-26 17:57 ` Mike Kazantsev [this message]
2009-01-26 23:17 ` Neil Bothwick
2009-01-26 17:57 ` Dale
2009-01-26 18:17 ` Grant
2009-01-26 18:26 ` Dale
2009-01-26 19:25 ` Paul Hartman
2009-01-26 20:21 ` Grant
2009-01-26 18:02 ` Rumen Yotov
2009-01-26 18:29 ` Daniel Pielmeier
2009-01-26 20:17 ` Grant
2009-01-26 20:24 ` Jesús Guerrero
2009-01-26 20:30 ` Grant
2009-01-26 20:44 ` Paul Hartman
2009-01-26 20:45 ` Paul Hartman
2009-01-26 20:51 ` Jesús Guerrero
2009-01-26 22:51 ` Grant
2009-01-27 14:29 ` Stroller
2009-01-27 15:29 ` Hieu, Luu Danh
2009-01-27 22:34 ` Grant
2009-01-27 22:57 ` Paul Hartman
2009-01-26 20:44 ` Daniel Pielmeier
2009-01-26 22:31 ` Grant
2009-01-26 19:57 ` Jesús Guerrero
2009-02-15 20:49 ` Alex Schuster
2009-02-16 18:33 ` Grant
2009-02-16 18:41 ` Dirk Heinrichs
2009-02-16 20:31 ` Grant
2009-02-16 20:40 ` [gentoo-user] " Nikos Chantziaras
2009-02-16 20:48 ` Dirk Heinrichs
2009-02-16 20:54 ` Nikos Chantziaras
2009-02-16 21:09 ` Dirk Heinrichs
2009-02-17 18:22 ` Grant
2009-02-17 18:35 ` Dirk Heinrichs
2009-02-16 20:43 ` [gentoo-user] " Dirk Heinrichs
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=20090126225713.1df20509@coercion \
--to=mike_kazantsev@fraggod.net \
--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