Paul Eggert <[EMAIL PROTECTED]> writes: > Yoann Vandoorselaere <[EMAIL PROTECTED]> writes: > >> warning: argp is LGPL but depend on exitfail which is GPL >> warning: canon-host is LGPL but depend on intprops which is GPL >> warning: euidaccess is LGPL but depend on exitfail which is GPL >> warning: fts-lgpl is LGPL but depend on exitfail which is GPL >> warning: fts-lgpl is LGPL but depend on fcntl-safer which is GPL >> warning: fts-lgpl is LGPL but depend on intprops which is GPL >> warning: fts-lgpl is LGPL but depend on unistd-safer which is GPL >> warning: getaddrinfo is LGPL but depend on intprops which is GPL >> warning: inttostr is LGPL but depend on intprops which is GPL >> warning: obstack is LGPL but depend on exitfail which is GPL > > I haven't waded through that whole list, but I'm a bit antsy about > wholesale conversion of gnulib to the LGPL. Isn't thee a better > way?
I don't see a move to make all of gnulib LGPL here -- what I see are some accidental dependencies on GPL'd moduled by LGPL'd modules. I wrote the getaddrinfo module for LGPL'ed applications/libraries, and having it depend on GPL'ed modules defeats the purpose of that module. The argp module comes from glibc, under LGPL, and any GPL'ed dependency seem counter-productive. I can't speak for the other examples, but at least that is two. Hopefully, if Yoann can supply some mechanism to detect this problem automatically, we will detect these problems immediately in the future. /Simon
