Adding gnulib to our source code might not be the best solution. The gnulib
page manual says that systems that are not glibc based are occassionally
tested at best. Their list of supported platforms is not very extensive
either.

In addition this is a source code library, which means _WE_ will have to
make sure we copy & paste the code on the right places. I see this as a
real stopper.


2013/10/22 Dimitrios Apostolou <notifications@github.com>

> In libpromises/signals.c:
>
> > @@ -52,6 +102,28 @@ void HandleSignalsForAgent(int signum)
> >          LogSetGlobalLevel(LOG_LEVEL_NOTICE);
> >      }
> >
> > +    unsigned char sig = (unsigned char)signum;
>
> Indeed, a quick search reveals that blocking operations should be avoided
> on Windows. I'm tired of this platform's non-POSIX compliance, I'm planning
> to raise the issue of importing gnulib modules into Core. Now that Core is
> fully GPL and open source, even when used in Enterprise, this should be
> feasible and save us of *lots* of portability trouble.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/cfengine/core/pull/1031/files#r7127000>
> .
>