Peter Humphrey wrote: > On Tuesday 04 Apr 2017 17:52:30 Dale wrote: >> Peter Humphrey wrote: >>> Has anyone else noticed that running "eclean-pkg -d" removes all >>> packages, or nearly so? I've had it happen recently on a few amd64 >>> systems and an x86 system, and it's becoming annoying. Well, no, >>> actually it's long since become annoying. >> If it is removing to much, leave out the -d option. With -d, it only >> leaves the minimum needed to re-emerge the packages currently >> installed. It works the same way with -dist as well. From the man page: >> >> -d, --deep only keep the minimum for a reinstallation >> >> I think if you leave off the -d option it leaves anything that is still >> in the tree, may include overlays as well. > Yes, I've done that of course. The point is that it used to work with -d, > and now it doesn't. If you ask how I know it used to work, my answer is that > of course I don't, but at least it only removed a sensible-looking number of > packages. > > The other day I was left with just six package files and the directory > structure. > > I haven't noticed a problem with eclean-dist. >
I just tested it here and it works as expected. It left about 1500 files in my packages directory. I'm using gentoolkit-0.4.0 here. If you are using something different, may want to try it. I use that pretty regular and its always worked as it should for me. If you are only left with 6 packages, something isn't right somewhere. Have you checked to be sure it is still saving a tarball of each installed package? Maybe something was changed in make.conf and it isn't building new ones for some reason, a errant edit maybe. May want to build a new package and check to confirm it saved it or not. If we compare what I have that works with what you have, maybe we can figure out what is making this not work. Clearly something isn't working. Dale :-) :-)
