On May 6, 2009, at 10:59 AM, Todd Zullinger wrote:

> Stephen John Smoogen wrote:
>>
>> On Tue, Apr 21, 2009 at 11:34 AM, James Turnbull
>> <[email protected]> wrote:
>>> R.I.Pienaar wrote:
>>>> - The file 'COPYING' is not included anymore, the redhat spec file
>>>> still mentions it though, either add the file or just remove it
>>>> from line 63 of conf/redhat/facter.spec
>>>
>>> Noted thanks.
>>
>> Is there a reason it is not included anymore?
>
> In the facter-1.5.4 tarball, COPYING was identical to the LICENSE
> file, which is still included in the 1.5.5rc1 tarball.  But I think
> there is a bit of a problem still.
>
> In a86577c (Fixing the GPL/LGPL incompatibility by choosing the
> oldest-mentioned license (GPL)), COPYING was removed and LICENSE was
> modified.  Prior to this commit, COPYING was the LGPLv2 and LICENSE
> was text similar to what is included in puppet, stating that facter is
> made available under the terms of the GPLv2 or later.  But with
> a86577c, LICENSE was updated to GPLv3.  I am guessing this was not the
> real intention?
>
> Perhaps a proper fix would restore the previous LICENSE file and
> update the COPYING file to reflect the GPLv2 content from
> http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt ?

Yes, that's the right approach.  I'd like Facter under the LGPL, but I  
haven't tracked the license file changes enough to know what happened  
when.

I'll get it all figured out and straightened up next week.


-- 
This book fills a much-needed gap. -- Moses Hadas
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to