1 |
On Thu, 25 Dec 2014 10:03:05 +0000 (UTC) |
2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
3 |
|
4 |
> Zac Medico posted on Wed, 24 Dec 2014 00:13:57 -0800 as excerpted: |
5 |
> |
6 |
> >> If there were some way to |
7 |
> >> get all the info for the binpkgs into one file (so it could be run |
8 |
> >> on cron or something), this could mean that I'd only have to do |
9 |
> >> one file request for all that metadata and would be much quicker |
10 |
> >> than inspecting all those files. |
11 |
> > |
12 |
> > That's what $PKGDIR/Packages is. |
13 |
> |
14 |
> This is a good excuse to ask a question that has bothered me for some |
15 |
> time, plus make a request for the new eclean-pkg replacement... |
16 |
> |
17 |
> Normally I like to keep several old binpkgs around for |
18 |
> troubleshooting reference or quick-install, but the combined set of |
19 |
> kde packages, for instance, can get pretty big, and with monthly |
20 |
> iterations, they build up pretty fast. |
21 |
> |
22 |
> But eclean-pkg doesn't have an easy way to say clean up /just/ |
23 |
> kde-base/ *, leaving the currently installed version and one previous |
24 |
> version for reference, cleaning out all others. (Sure I could |
25 |
> put /everything/ else on the exclude list, but what's really needed |
26 |
> is an include list, plus a "keep N more" option.) |
27 |
> |
28 |
> So I often end up cleaning packages like that out manually by simply |
29 |
> deleting them. My question is thus, does the remaining |
30 |
> index/db/cache entry get cleaned properly (when?) or am I leaving |
31 |
> uncleanable garbage behind when I do this? |
32 |
> |
33 |
> Which of course translates into a couple of feature requests for the |
34 |
> new eclean-pkg: |
35 |
> |
36 |
> 1) Make it possible to clean only selected pkgs or categories. |
37 |
> |
38 |
> 2) Have an option to clean up and/or regenerate the cache/index/db/ |
39 |
> whatever files, re-syncing them with what's actually there. |
40 |
> |
41 |
> |
42 |
... |
43 |
|
44 |
> But of course that does make having an automated cleaner that can |
45 |
> keep just the last N package versions around while deleting the |
46 |
> others, that much more important. |
47 |
> |
48 |
|
49 |
Please file a feature request bug for gentoolkit/eclean. |
50 |
|
51 |
If I can ever get caught up with other things or we get a gsoc student |
52 |
that needs some extra work... |
53 |
|
54 |
Also with eclean and emaint rewritten (by me) so that eclean could use |
55 |
emaint modules directly. I have thought a few times we might migrate |
56 |
eclean from gentoolkit to emaint module(s) They can even be installed |
57 |
separately from portage via ebuild. The emaint system is fully modular |
58 |
with a plug-in system. |
59 |
|
60 |
-- |
61 |
Brian Dolbec <dolsen> |