Gentoo Needs to have a Cruft script/system built into it! Reproducible: Always Steps to Reproduce: 1.Run any 3 party cruft script and find Cruft on the system with these unreliable scripts. 2. 3. Actual Results: To many FALSE reports Expected Results: Need a accurate script to do the job correct The Gentoo team needs to put togther a offical Cruft system/script into Gentoo.
Please, explain better what are you requesting...
I'm requesting that the Gentoo team please deal with the issues of Cruft in Gentoo, and make a script that works properly so people can remove it. I mean why is there so much Cruft getting left in the system. And why are there so many 3rd party scripts to remove this, are these just Gentoo zealots and there is no need for this, or is Gentoo installing things not correct so that the system does not reconize things that are there, and thinks that legitimate things are not. Either way, there seems to be alot of people concerned with Cruft and at this point so am I, and I want to ask that the Gentoo team develop either a system to deal with this, or a offical gentoo script that is apart of Gentoo to help users clean it up. Any way you look at it we need a way that either Gentoo installs and uninstalls better or scripts to help keep things well maintained. Thank you very much for your time and help in this matter.
(In reply to comment #2) > I'm requesting that the Gentoo team please deal with the issues of Cruft in > Gentoo, and make a script that works properly so people can remove it. $ esearch cruft [ Results for search key : cruft ] [ Applications found : 0 ] > I mean why is there so much Cruft getting left in the system. And why are there > so many 3rd party scripts to remove this, are these just Gentoo zealots and > there is no need for this, or is Gentoo installing things not correct so that > the system does not reconize things that are there, and thinks that legitimate > things are not. Now seriously - define "cruft" first, otherwise this makes really no sense.
Sorry what are you talking about with this comment: Now seriously - define "cruft" first, otherwise this makes really no sense. Please look at this: http://gentoo-wiki.com/TIP_Clean_Up_Cruft
(In reply to comment #4) > Sorry what are you talking about with this comment: > > Now seriously - define "cruft" first, otherwise this makes really no sense. About definition of cruft. "Files and directories that don't belong to any package" is not a definition, or would you like a script that will wipe /home, ccache directories, that will wipe your webs in /var/www and your databases, or what is actually this bug about? If an ebuild does not clean up the files after itself, then file a bug about *the ebuild which is broken*... Closing.
Gentoo is a new distro to me, but I have been running Linux many years on many other distros, all I can say is I have seen Cruft scripts out there one from Ed Catmur, so when you said explain this I was at a real loss as to what you meant, I just thought this was a common thing going on with Gentoo is all. So I guess something like Ed Catmur's script there should not be something like this incorporated as a offical script into Gentoo? Thanks
(In reply to comment #6) > Gentoo is a new distro to me, but I have been running Linux many years on many > other distros, all I can say is I have seen Cruft scripts out there one from Ed > Catmur, so when you said explain this I was at a real loss as to what you meant, > I just thought this was a common thing going on with Gentoo is all. If an ebuild leaves some files when uninstalled (except for configuration files that are in CONFIG_PROTECT directories), then it is a bug in that ebuild. But that is definitely not something common in Gentoo as a whole. > So I guess something like Ed Catmur's script there should not be something like > this incorporated as a offical script into Gentoo? If you want a slim system, there are things like FEATURES="noman noinfo nodoc" (see make.conf), there is userlocales use flag for glibc, if you don't need support for other language locales, put -nls into USE section in make.conf. There are other things being worked on (like removing unmodified protected files when unmerging an ebuild) or installing only those locales that are definined in LINGUAS (see 96283). But using a script that somewhat heuristically determines which files are not needed is definitely not the way to go. Hope that helps.
