public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfsprogs/xfsdump: what flavor of GPL...?
Date: Fri, 17 Aug 2007 08:44:30 -0500	[thread overview]
Message-ID: <46C5A63E.5070906@sandeen.net> (raw)
In-Reply-To: <46C3CC46.8030005@redhat.com>

Eric Sandeen wrote:
> Fedora is making a push to clarify licensing on all packages -
> 
> GPL+, GPLv2, GPLv2+, GPLv3, GPLv3+, LGPLv2, LGPLv2+, LGPLv3, LGPLv3+
> 
> are the acceptable license tags for rpm packaging at this point. ("+"
> means "or later").

Of course, the tag I put on the package is in no way binding for sgi -
it's just supposed to reflect the license inside.  But it does point out
a bit of confusion now that gplv3 is on the scene.

I'll follow fedora guidelines & put GPL+ and LGPLv2+ in the field for
now; when I get clarification from SGI I'll fix up if needed.

Thanks,
-Eric

> Looking, for example, at mkfs/xfs_mkfs.c:
> 
>  * This program is free software; you can redistribute it and/or
>  * modify it under the terms of the GNU General Public License as
>  * published by the Free Software Foundation.
> 
> it makes no mention of GPL _version_.
> 
> With all the ruckus lately over GPLv3, could sgi please clarify?  Since
> the included COPYING file says LGPL 2.1 and GPL2, I assume that LGPLv2
> and GPLv2 are appropriate for the package.
> 
> It'd be tedious, but you may wish to specify exactly which version of
> the license in the actual source files...
> 
> Thanks,
> 
> -Eric
> 
> 

      reply	other threads:[~2007-08-17 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-16  4:02 xfsprogs/xfsdump: what flavor of GPL...? Eric Sandeen
2007-08-17 13:44 ` Eric Sandeen [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46C5A63E.5070906@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=sandeen@redhat.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox