Leon Timmermans
Leon Timmermans
> Yeah, although if the concern is avoiding the window for another SIGHUP in the handler function before exec, wouldn't it be better to unblock SIGHUP unconditionally in the main...
> @Leont seemed unhappy about the alternative proposed in the last patch, (although he didn't really explain why, and for some reason I only see that comment in my mail,...
> Thanks, this made me reread relevant parts of the POSIX module and perlipc man pages and realize that handlers created with POSIX::SigAction have the "safe" flag off, making them...
> Apparently safe signals are incompatible with SA_NODEFER Just great! /s > I really don't think the distinction is moot (you can use sigaction() to install both safe and unsafe...
I thought we couldn't use this in public headers because C++?
> Can't call method "relative" on an undefined value at ...blib\lib/Path/Class/Entity.pm line 71. That suggests that `$self->new(...)` can return undef, which feels wrong. Apparently that happens if the argument to...
> Yeah, File::Spec provides no official way to work with paths using the semantics of a specified (as opposed to the native) OS. That You can just use `File::Spec::Unix` instead?
> Maybe we should change ExtUtils::MakeMaker to use ptar if available instead? Honestly, the last thing MakeMaker needs is new responsibilities.
> What do you mean by a new responsibilities? Figuring out "do we have a working ptar" or "do we have a working gnu tar", and in particular doing so...
Probably, this behavior should be an option, regardless of what's the default