There are created there by lots of ebuilds so that portage leaves the subdirectories alone and doesn't unmerge them, don't wipe the .keep* files in subdirs please.
i've backported `checkpath` to baselayout-1.12 for people to use *** This bug has been marked as a duplicate of bug 192682 ***
I'm afraid I really don't understand this solution. Every baselayout out there wipes .keep*, including 2.0.0_rc6-r1. # Clean up /var/run and create /var/run/utmp so we can login. for x in $(find /var/run ! -type d ! -name utmp ! -name innd.pid \ ! -name random-seed ! -name ld-elf.so.hints ! -name ld.so.hints); do [ ! -f "${x}" ] && continue ... rm -f "${x}" done
(In reply to comment #1) > i've backported `checkpath` to baselayout-1.12 for people to use Reopen, this is completely unrelated per discussion w/ Uberlord. bootmisc doesn't use checkpath in any way.
I think the argument is that per package init scripts should use checkpath to ensure the directory exists with the correct uid/gid and permissions.
OK, so you suggest going across the entire tree looking for ebuilds that keepdir subdirectories in /var/run with specific permissions - instead of simply not nuking stuff that's not supposed to be nuked at all in the first place? Well have fun with that, I plain don't have time for this. These ebuilds create the directories for a reason and it takes like 5 seconds to fix baselayout's bootmisc initscript to leave .keep* stuff alone. Thanks.
then dont open bugs if you dont have time for that *** This bug has been marked as a duplicate of bug 192682 ***
(In reply to comment #6) > then dont open bugs if you dont have time for that Yup. Since for every trivial problem, there's always a complicated solution that will take months to implement and involve tens of people instead of choosing a trivial fix that would take care of this in one minute. This bug proves it once again. So yeah, thanks very much again, sorry for bothering you.
the choices are: - implement a small change in one place that doesnt account for all situations and is not correct but allows most people to go on in ignorance - correctly implement changes in every place that it is needed and accounts for all situations and allows for all people to go on in ignorance i obviously choose the latter, as this bug proves once again
