On Friday 09 June 2006 20:25, Andrew Ross wrote:
> Apologies if this has been addressed previously,

i dont believe it has ever come up before

> Is there any sort of policy covering how an ebuild should deal with
> /var/cache during unmerge?

maybe give ebuilds a way to maintain a list of files that portage should nuke 
when unmerging the package ...

> A similar issue exists with log files, but I'd expect them to occupy
> less space than caches, and generally be considered more useful (since
> they can't be regenerated). If they were to be dealt with, perhaps
> portage could have a purge option that removes all traces of a package
> from the system - including log and cache files (it looks like temp
> files should already be cleaned out by the ebuild).

i'm not so sure ... i'd guess that the large majority of packages do logging 
with syslog() and there really is no way to bind <logfile name> to <package> 
sanely for all system loggers out there

however, logs that a daemon itself generates/maintains rather than using the 
system logger would fall into this discussion
-mike