| 1 |
On Friday 09 June 2006 20:25, Andrew Ross wrote: |
| 2 |
> Apologies if this has been addressed previously, |
| 3 |
|
| 4 |
i dont believe it has ever come up before |
| 5 |
|
| 6 |
> Is there any sort of policy covering how an ebuild should deal with |
| 7 |
> /var/cache during unmerge? |
| 8 |
|
| 9 |
maybe give ebuilds a way to maintain a list of files that portage should nuke |
| 10 |
when unmerging the package ... |
| 11 |
|
| 12 |
> A similar issue exists with log files, but I'd expect them to occupy |
| 13 |
> less space than caches, and generally be considered more useful (since |
| 14 |
> they can't be regenerated). If they were to be dealt with, perhaps |
| 15 |
> portage could have a purge option that removes all traces of a package |
| 16 |
> from the system - including log and cache files (it looks like temp |
| 17 |
> files should already be cleaned out by the ebuild). |
| 18 |
|
| 19 |
i'm not so sure ... i'd guess that the large majority of packages do logging |
| 20 |
with syslog() and there really is no way to bind <logfile name> to <package> |
| 21 |
sanely for all system loggers out there |
| 22 |
|
| 23 |
however, logs that a daemon itself generates/maintains rather than using the |
| 24 |
system logger would fall into this discussion |
| 25 |
-mike |
Archives