unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: mhw@netris.org
To: Eric Bavier <ericbavier@gmail.com>
Cc: guix-devel@gnu.org, "Bishmer J. Sekaran" <bishmer@scorpionrock.com>
Subject: Re: [PATCH] Add dcfldd
Date: Tue, 12 Aug 2014 23:34:27 -0400	[thread overview]
Message-ID: <877g2dnjuk.fsf@netris.org> (raw)
In-Reply-To: <87vbpxenrv.fsf@gmail.com> (Eric Bavier's message of "Tue, 12 Aug 2014 10:22:12 -0500")

Eric Bavier <ericbavier@gmail.com> writes:

> Bishmer J. Sekaran writes:
>
>> re: Licensing, my impression was that "gpl2+" only applies if the 
>> authors specifically invoke "any later version" when they distribute the 
>> software, per clause 9 of the GPL 2
>
> [...]
>
>> Upstream lists the project as:
>> "License
>> GNU General Public License version 2.0 (GPLv2)"
>> http://sourceforge.net/projects/dcfldd/
>>
>> Am I in error?
>
> In some cases the "or later" clause is only mentioned in the source file
> headers.  I see, from a brief glance at the source, that this is the
> case for dcfldd.

I believe the copyright notices in the source files are ultimately what
determines the license.  If the source files include copyright notices
with the "any later version" language, then the license is in fact
gpl2+.  This is also my expectation given that 'dcfldd' was forked from
GNU dd, which was presumably covered by gpl2+ at the time of the fork.

     Thanks!
       Mark

  reply	other threads:[~2014-08-13  3:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12 15:07 [PATCH] Add dcfldd Bishmer J. Sekaran
2014-08-12 15:22 ` Eric Bavier
2014-08-13  3:34   ` mhw [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-12 15:00 Bishmer J. Sekaran
2014-08-12 18:27 ` Ludovic Courtès
2014-08-04  3:25 Bishmer J. Sekaran
2014-08-04 12:00 ` Bishmer J. Sekaran
2014-08-06 17:17   ` Andreas Enge
2014-08-11  5:36   ` Mark H Weaver

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=877g2dnjuk.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=bishmer@scorpionrock.com \
    --cc=ericbavier@gmail.com \
    --cc=guix-devel@gnu.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).