Re: [gentoo-dev] Dealing with /var/cache on unmerge
Daniel Drake wrote: Mike Frysinger wrote: maybe give ebuilds a way to maintain a list of files that portage should nuke when unmerging the package ... Something similar to this would be useful for kernel ebuilds, as simply unmerging kernel source will leave a load of temporary and object files on the filesystem. Daniel Already been there and got removed, because it broke emerge -e world for ebuilds that need configured kernel to compile. -- Best regards, Jakub Moc mailto:[EMAIL PROTECTED] GPG signature: http://subkeys.pgp.net:11371/pks/lookup?op=getsearch=0xCEBA3D9E Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E ... still no signature ;) signature.asc Description: OpenPGP digital signature
Re: [gentoo-dev] Dealing with /var/cache on unmerge
On Sunday 11 June 2006 05:01, Jakub Moc wrote: Daniel Drake wrote: Mike Frysinger wrote: maybe give ebuilds a way to maintain a list of files that portage should nuke when unmerging the package ... Something similar to this would be useful for kernel ebuilds, as simply unmerging kernel source will leave a load of temporary and object files on the filesystem. Already been there and got removed, because it broke emerge -e world for ebuilds that need configured kernel to compile. that isnt a bug you cant assume the kernel sources that were just dropped into place match exactly the compiled objects in the same tree -mike pgpJwABwgWcmr.pgp Description: PGP signature
Re: [gentoo-dev] Dealing with /var/cache on unmerge
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 pgprI9bXGa4EW.pgp Description: PGP signature
Re: [gentoo-dev] Dealing with /var/cache on unmerge
Mike Frysinger wrote: maybe give ebuilds a way to maintain a list of files that portage should nuke when unmerging the package ... Something similar to this would be useful for kernel ebuilds, as simply unmerging kernel source will leave a load of temporary and object files on the filesystem. Daniel -- gentoo-dev@gentoo.org mailing list
[gentoo-dev] Dealing with /var/cache on unmerge
Apologies if this has been addressed previously, but my searches of the Gentoo website, devmanual, forums, and mailing list archives didn't turn up anything definitive. Is there any sort of policy covering how an ebuild should deal with /var/cache during unmerge? The devmanual pages for pkg_prerm (http://tinyurl.com/huh7n) and pkg_postrm (http://tinyurl.com/f5b7o) are the closest I've come to an answer, but I don't consider deletion of the cache dir to be the same as updating it. I've looked at a few ebuilds in the tree (including samba and squid) and they seem to leave in place any cache files created during normal execution of the package in question. This means that after an unmerge the sysadmin needs to go and clean out /var/cache/whatever. During ebuild development and testing, I can see why one might want the cache files to remain, so unconditional cleaning of /var/cache is out of the question. However, removing of cache files could be controlled by a FEATURE (eg. keepcache - unless that implies the retention of cache files from the original merge a la keepwork and keeptemp). 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). Of course, the general opinion might be that management of /var/cache is outside the scope of portage, and best left to the sysadmin (and/or an separate automated tool), although the FHS doesn't specify either way (http://tinyurl.com/26gpd). That's fine with me, but I think it's good to have this on record in the mailing list archives, and perhaps in the devmanual as well. Cheers Andrew -- gentoo-dev@gentoo.org mailing list
