]> git.ipfire.org Git - thirdparty/libvirt.git/commit
maint: follow recommended practice for using LGPL
authorEric Blake <eblake@redhat.com>
Tue, 14 May 2013 23:25:02 +0000 (17:25 -0600)
committerEric Blake <eblake@redhat.com>
Mon, 20 May 2013 20:15:21 +0000 (14:15 -0600)
commitde483052a23afa65b7093e002e26eb27868ac479
tree5eec69f18a10bab3724d8f3319b39b8e246abd6e
parentd7f53c7b97475ac9db8cb45aa5c314931f20d001
maint: follow recommended practice for using LGPL

https://www.gnu.org/licenses/gpl-howto.html states:

You should also include a copy of the license itself somewhere in the
distribution of your program. All programs, whether they are released
under the GPL or LGPL, should include the text version of the GPL. In
GNU programs the license is usually in a file called COPYING.

If you are releasing your program under the LGPL, you should also
include the text version of the LGPL, usually in a file called
COPYING.LESSER. Please note that, since the LGPL is a set of
additional permissions on top of the GPL, it's important to include
both licenses so users have all the materials they need to understand
their rights.

* configure.ac (COPYING): No more games with non-git file.
* COPYING: New file, copied from gnulib.
* COPYING.LIB: Rename...
* COPYING.LESSER: ...to this.
* .gitignore: Track licenses in git.
* cfg.mk (exclude_file_name_regexp--sc_copyright_address): Tweak
rule.
* libvirt.spec.in (daemon, client, python): Reflect rename.

Signed-off-by: Eric Blake <eblake@redhat.com>
.gitignore
COPYING [new file with mode: 0644]
COPYING.LESSER [moved from COPYING.LIB with 100% similarity]
cfg.mk
configure.ac
libvirt.spec.in