Ports that touch the filesystem before install
crees at marcuscom.com
Sun Jun 5 04:22:16 EDT 2011
I know Tinderbox checks whether something's touched the filesystem by
looking at the state before and after...
which leads to cases like Mailman which touch the filesystem during
configure and then compensate (with a comment to say this is what it's
doing!) by removing the directory created... These are now causing
problems for me while I convert them to use USERS .
Clearly this is unacceptable??
Perhaps we could set some options on the nullfs mount to make all but
WRKDIR read-only until the install phase? This should weed out the
ports that do that!
It's also biting me with qmail at the moment :(
Anyone have any better ideas, or tell me it's not a problem?
More information about the tinderbox-list