Re: gplv3 files and updates

[Brett Smith]

On Mon, Jul 16, 2007 at 09:00:32AM +0200, Jim Meyering wrote:
> > importing gnulib), see [1]. Look at the variable 'gnulib_version': If you 
> > set
> > it to a date in the past, you eliminate this sort of trouble. And if you
> > set it to 'HEAD', you track all changes like you currently do. If the
> > coreutils 'bootstrap' script had the same configuration parameter, you would
> > only - at some point before the release - change this variable from HEAD
> > to the the current date, until after the release.
> 
> That sounds reasonable.
> However, I'm not likely to make bootstrap do this in the next few weeks.
> Are you?

Has any progress been made on this?  I bring this up now because we just
got a question at <address@hidden> that was based on exactly the kind of
confusion I was worried about: an LGPLed project was using gnulib files
without changing the license headers, and so this person was concerned that
they might be bound by the GPL instead -- there wasn't any gnulib
documentation or other information in the project tarball to suggest
otherwise, after all.

If the solution has already been implemented and the problem this user
stumbled upon is historical cruft, then that's great; I just wanted to
check.

Thanks,

-- 
Brett Smith
Licensing Compliance Engineer, Free Software Foundation