I noticed this upon emerging anacron without realising that I had emerged it already some time ago. Upon the first merge, things are setup as expected. But if one then merges it again then it removes the /var/spool/anacron directory during the clean stage (because it's empty and thus, considered a valid candidate for removal). This breaks anacron of course. Naturally, this won't happen if /var/spool/anacron is populated between invocations - as it probably would have been in my case had I made any use of the program before any subsequent merge operations. My suggestion is to change line #35 of "anacron-2.3-r2.ebuild" so that it makes use of the keepdir function instead of dodir: keepdir /var/spool/anacron I would be grateful if this this fix could be applied at the herd's earliest convenience. Thanks.
Furthermore, if there is still a genuine requirement to clean up this directory after a removal then I suppose one could use the pkg_postrm() function to nuke the directory although I wouldn't be in favour of such a technique myself.
(In reply to comment #1) > Furthermore, if there is still a genuine requirement to clean up this directory > after a removal then I suppose one could use the pkg_postrm() function to nuke > the directory although I wouldn't be in favour of such a technique myself. The ebuild wasn't trying to clean up anything; that's just what happens when dodir is used where keepdir should be used. In cvs.
I know - that's why I filed it as a bug, after all. I was just thinking out aloud (the spool data can probably be considered cruft upon removal of this packet). Thanks.
