Hi Reuben, > On Mon, 30 Dec 2013 at 09:28, Reuben Thomas <r...@sc3d.org> wrote: > > > On 30 December 2013 08:18, Reuben Thomas <r...@sc3d.org> wrote: > > > >> > >> On 30 December 2013 01:20, Paul Eggert <egg...@cs.ucla.edu> wrote: > >> > >>> Reuben Thomas wrote: > >>> > >>>> It's been drawn to my attention that under some circumstances, gnulib > >>>> fails > >>>> to include progname when it's needed > >>>> > >>> > >>> That's documented here: > >>> > >>> > >>> http://www.gnu.org/software/gnulib/manual/html_node/error-and-progname.html > >>> > >> > >> Thanks. Could it be documented in a warning message (either produced by > >> gnulib-tool or at compile time)? The way it fails gives no reason to > >> suspect it's not a bug. > >> > > > > Come to that, it's a pity to impose this on users who haven't told gnulib > > not to include GPL'ed modules. Or is it not possible to LGPL progname? > > > > I just ran into this again. Would it be possible to LGPL progname?
We do not want to put 'progname' under LGPL license, because 'progname' is meant to be used in programs, not libraries, and for programs the GPL is the right license. But things have changed since 2013: Gnulib modules that can reasonably be used in libraries now depend on 'getprogname' instead of 'progname' [1]. Bruno [1] https://lists.gnu.org/archive/html/bug-gnulib/2016-08/msg00040.html
