| 1 |
2010/3/20 Brian Dolbec <brian.dolbec@×××××.com>: |
| 2 |
> Dmitry, eclean is written in python same as portage. For it to |
| 3 |
> integrate into eclean it too would also need to be written in python. |
| 4 |
> Unfortunately your script would not fit. |
| 5 |
> |
| 6 |
> There are 2 pieces of information that would be required from the client |
| 7 |
> pc's the installed pkg list and the exclude file. The exclude file |
| 8 |
> being a debatable one. Since portage now needs a min. of python-2.6 it |
| 9 |
> should be possible for the network eclean module to import portage from |
| 10 |
> the client machine and obtain the installed pkg list. From there it |
| 11 |
> would be added to a global installed pkgs list that would then remove |
| 12 |
> any source files they claim to own. I think all other info and checks |
| 13 |
> would be handled by the eclean app running on the server. |
| 14 |
> |
| 15 |
> As for the exclude file it may need to be transferred and parsed to |
| 16 |
> accumulate the results (trickier, due to possible conflicts). |
| 17 |
> alternatively that control might be better left controlled only on the |
| 18 |
> server. |
| 19 |
> |
| 20 |
> Eclean would not need to installed on the client machines at all. |
| 21 |
> |
| 22 |
> P.S. eclean assumes all files dirty and in need of cleaning unless |
| 23 |
> proven otherwise (due to the dynamic nature of the tree). |
| 24 |
> -- |
| 25 |
> Brian Dolbec <brian.dolbec@×××××.com> |
| 26 |
> |
| 27 |
|
| 28 |
Thanks for explanation, Brian. I was misleaded that you interested in |
| 29 |
any working solution including bash script. |
Archives