On 11/23/10 13:15, Eric Blake wrote: > Should we instead patch gnulib's open() module to work around this bug, > so that tar can just rely on the gnulib module for POSIX semantics > instead of having to copy this workaround into all clients?
That might be a good idea, yes. I'd first like to see FreeBSD's justification for being nonstandard, though; if it's a good one we may want to leave 'open' alone (some apps might care about the difference maybe?). Right now I expect only 'tar' cares about this particular failure mode, and that it's not urgent to propagate it into gnulib. > At any rate, this should be documented in gnulib's list of portability > pitfalls. Yes.