public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Installing outside of Portage & cruft removal
Date: Mon, 26 Jan 2009 10:17:43 -0800	[thread overview]
Message-ID: <49bf44f10901261017u5bec6a38yc9cbe9f2bf864421@mail.gmail.com> (raw)
In-Reply-To: <497DF993.9090905@gmail.com>

>>>> What do you guys think of this?  Do you know of a good cruft removal script?
>>>>
>>> Yep, there's quite good one in gentoo itself.
>>>
>>> Basically, you'll need to write a short config for it, consisting of
>>> lines like "cruft name", "cruft src uri" and a few more lines if you'll
>>> need to pass some extra parameters to configure/make/install.
>>> It'll build the package in a sandbox, then transfer it to destination,
>>> memorizing every change it did and preventing collisions and config
>>> overwrites.
>>>
>>> Just put that config script into an ebuild file and use portage to
>>> build it - as simple as it gets ;)
>>>
>>
>> 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 ~/.*
>>
>> - Grant
>>
>>
>>
>
[snip]
> You have to clean out /etc and home directories yourself.

Exactly.  Nothing to help me along?  I'll check out qfile, but I'm
surprised there isn't a good script for this.

I'm the only one interested in a filesystem audit?

- Grant


> Portage does do a good job of removing all the other files tho.  If it
> puts it there, it will remove it if you unmerge a package.
>
> Dale



  reply	other threads:[~2009-01-26 18:17 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
2009-01-26 23:17       ` Neil Bothwick
2009-01-26 17:57     ` Dale
2009-01-26 18:17       ` Grant [this message]
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=49bf44f10901261017u5bec6a38yc9cbe9f2bf864421@mail.gmail.com \
    --to=emailgrant@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