public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: james <garftd@verizon.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Replacement for gcruft: gcrud
Date: Thu, 16 Aug 2018 14:22:38 -0400	[thread overview]
Message-ID: <356bd469-39a4-607f-ff68-8f1d18c52fb3@verizon.net> (raw)
In-Reply-To: <32db6b65-f082-9189-8a4d-047005b980f9@gmail.com>

On 08/16/18 02:07, Andrew Udvare wrote:
> gcruft seems to have died off (https://www.google.com/search?q=gcruft
> only returns ebuild results). 

It might (not really sure) be active but it appears to still be around
as ebuilds::

eix -R gcruft
* app-portage/gcruft
     Available versions:  ~0.1-r1^m[1] ~0.1-r1^m[2] ~0.1.1^m[1] ~0.1.1^m[2]
     Homepage:            http://www.genoetigt.de/site/projects/gcruft
     Description:         helps finding orphaned files on a gentoo system





> I was using it quite a lot and wrote many
> exception files. It's gone now with no way for my or anyone else's
> ebuild to get the original source. I did preserve it though, here:
> https://gitlab.com/Tatsh/gcruft

Thanks for caring!


> I wrote a replacement in C named gcrud. It only needs GLib2 installed to
> work. It's much faster than gcruft ever was. The code is here:
> 
> https://gitlab.com/Tatsh/gcrud
> https://github.com/Tatsh/gcrud


It's going to take me a while to get aroud to testing, but I really
really like admin codes in "C" so it is automatically on my short list....

> 
> I am placing preference in GitLab for issues and merge requests, but I
> will accept PRs from GitHub.

I really like the like gitlab for a variety of reason. I sure wish some
would put together a gitlab-meta ebuild for gentoo. I'd like to house
codes locally, and export relevant open source codes to a online
location, or distributed among a collective of gitlab-gentoo sites.


Complementary to github and our github-centric-dev community.


> 
> The whitelist https://gitlab.com/Tatsh/gcrud/blob/master/whitelist.c is
> currently hard-coded and limited but the results are satisfactory for
> now in my use cases.
> 
> Type use case:
> 
> sudo ./gcrud | sort -u > out.log
> 
> Examine out.log for things you can delete. There are absolutely zero
> calls to delete files from the machine in my code and never will be any
> kind of automation support.

That your choice and I respect that call. However (and it's a big
however), my gentoo-centric HPC cluster do need automated system
cleanup. So, initial, it's be an army of scripts, similar to your code,
that is mandatory in a "loosely coupled" heterogeneous clusters, not to
mention first-line security related cleanup.

> If anyone tries it out I certainly would like to see your output and get
> some bug reports or suggestions. The main feature planned is reading
> from a configuration file for exact file paths and regexs.

Yes, but, it'll be  while for me. Offer and automated clean up option,
and I have dozens of systems to test.....
> 
> --
> Andrew

Thank you Andrew for your work. It can also be very useful to my DAG
efforts for compiling, verifying, and clean up of cluster codes.


GLEP 64 was on the path to systematically solve what you you are doing
after the fact::

https://wiki.gentoo.org/wiki/GLEP:64

More refs for your convenience

http://asic-linux.com.mx/~izto/checkinstall/

http://gittup.org/tup/
("It will automatically clean-up old files.")


hth,
James




  reply	other threads:[~2018-08-16 18:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16  6:07 [gentoo-user] Replacement for gcruft: gcrud Andrew Udvare
2018-08-16 18:22 ` james [this message]
2018-08-16 23:25   ` Andrew Udvare
2018-08-16 20:09 ` Corentin “Nado” Pazdera
2018-08-16 23:09   ` Andrew Udvare
2018-08-17 12:15   ` Corentin “Nado” Pazdera

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=356bd469-39a4-607f-ff68-8f1d18c52fb3@verizon.net \
    --to=garftd@verizon.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