Hi Simon, Simon Josefsson <[email protected]> skribis:
> Thank you! Does this make shepherd Debian packages useless, or can we suggest > people to ignore the warning? Any simple way to patch it out from within > shepherd? The Debian freeze is in two weeks and it would be nice to give a > good first impression to people try it shepherd from Debian… i could try to > get guile patched, but it is getting late. A simple way would be to patch out the ‘environ’ warning in Guile: it didn’t exist before 3.0.10, it’s bogus (it fires even when you’re not mutating the environment and even with just a single user thread, as is the case here), and the comment itself doesn’t change program behavior. If that’s not adequate, we could try and come up with a quick hack for shepherd to avoid the ‘environ’ call at the top-level (though that’s probably not something I would consider for inclusion in the Shepherd proper.) WDYT? Ludo’.
