[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Using gnulib build tools in a non-GPL project?

From: Assaf Gordon
Subject: Using gnulib build tools in a non-GPL project?
Date: Fri, 26 Apr 2013 14:22:04 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.4) Gecko/20120510 Icedove/10.0.4


Is it possible (legally) to use two gnulib scripts (git-version-gen and 
gitlog-to-changelog) in a non-GPL project? and if so, can the project be 1) 
BSD/MIT, and 2) proprietary/closed-source ? 
The two scripts are GPLv3+, and are categorized as "GPLed build tools".

The intended usage:
1. The project will use autoconf/automake
2. The scripts will be copied into the "build-aux" directory as-is, and will be 
used during development, but not modified.
3. The scripts will be distributed as-is with the source code of the rest of 
the project.
4. The project license file will clearly mention that those files are GPLv3+, 
while other files in the project are in another license.

To the best of my understanding, it's OK to use GPL'd tools in a non-GPL 
project, and this does not constitute "derivative work" - however I would 
appreciate an expert's advice about this.

The closest discussion I could find was "gnulib's licensing" thread ( 
http://lists.gnu.org/archive/html/bug-gnulib/2011-05/msg00103.html )      but 
it was more about using gnulib's C code modules.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]