Re: gnulib-tool: Stop doing license notice replacements

Eric Blake wrote: > > +reasonably be used in libraries, are under LGPL@. Few modules are > > +under other licenses, such as LGPLv2+, unlimited, or public domain. > > Would read better as "A few modules are..." Feel free to commit a correction, here and elsewhere. (I am not a native English speak

Re: put appropriate license notices in source files

Eric Blake wrote: > Speaking of tools, should we include SPDX tags alongside the full text > of all our licenses, as that is yet another thing that aids > license-checking tools? If there is a GNU policy on this, I would follow it. Personally I think there is little point to it. SPDX arose in the

Re: gnulib-tool: Stop doing license notice replacements

On Fri, Jun 04, 2021 at 10:29:22PM +0200, Bruno Haible wrote: > As agreed upon in the thread starting at > . > > > +++ b/doc/gnulib-intro.texi > @@ -455,15 +455,22 @@ proofreading the patch. > @section Copyright > > Most mo

Re: put appropriate license notices in source files

On 6/4/21 1:25 PM, Eric Blake wrote: Speaking of tools, should we include SPDX tags alongside the full text of all our licenses, as that is yet another thing that aids license-checking tools? That's not a job I'd care to take on, for reasons I discussed for tzdb last year (see the last paragra

gnulib-tool: Stop doing license notice replacements

As agreed upon in the thread starting at . 2021-06-04 Bruno Haible gnulib-tool: Stop doing license notice replacements. * gnulib-tool: Don't document --more-symlinks and --more-hardlinks any more.

Re: put appropriate license notices in source files

On Fri, Jun 04, 2021 at 10:03:04PM +0200, Bruno Haible wrote: > * There are many tools for copyright and license checking [2] and we make > their job easier by avoiding unclear situations regarding what is > "nontrivial". > So, I added copyright and license notices to these files. > > [1

Re: gnupload, git-merge-changelog: Fix module description

I did: > * modules/git-merge-changelog (License): Change to GPLv2+. That doesn't work: It produces gnulib-tool warnings gnulib-tool: warning: module git-merge-changelog depends on a module with an incompatible license: c-strstr gnulib-tool: warning: module git-merge-changelog depends on a

put appropriate license notices in source files

This series of patches puts into the source files (in lib/ and build-aux/) the license notices that match the module descriptions. What to do with tiny files that, so far, have no copyright notice? The Maintainers' Guide [1] allows to omit the copyright notice for "trivial" files. I find it reason

new directory with license notices

In preparation of the change of license notices, I'm adding suitable license notices, ready for copy&paste into the source files. While the vast majority of source files talk about "This program ...", config.guess and config.sub talk about "This file ...". I adopt this change for Gnulib, because G

gnupload, git-merge-changelog: Fix module description

In our current convention, when we talk about GPL we mean GPLv3+. The module 'git-merge-changelog', however, is meant to be GPLv2+, not GPLv3+ (for compatibility with git itself). And the module 'gnupload' is meant to be GPLv2+ as well. But gnulib-tool does not support build tools under GPLv2+ so

revamp check-copyright script

The check-copyright script needs a couple of changes, so that it does not get in the way of producing 0 failures. 2021-06-04 Bruno Haible Revamp check-copyright script. * check-copyright: Search only the first 50 lines of each file. Recognize 'LGPLv3+ or GPLv2+', 'unli