All of lore.kernel.org
 help / color / mirror / Atom feed
From: mjt@nysv.org
To: reiserfs-list@namesys.com
Subject: Re: reiser4progs 0.5.4 for Debian
Date: Mon, 7 Jun 2004 23:02:04 +0300	[thread overview]
Message-ID: <20040607200203.GL4990@nysv.org> (raw)
In-Reply-To: <20040607193305.GA4854@raptus.homelinux.org>

On Mon, Jun 07, 2004 at 09:33:05PM +0200, Domenico Andreoli wrote:

>> I know this is the wrong forum perhaps, but AFAIK the reiser4progs
>> maintainer(s) read this list..
>yes, i'm here listening in the darkness...

Some Debian developers are quite anal about these issues, indeed,
I got a bit flamed :)

But still, I didn't have your email and this seemed the proper, although
wrong from a debian point of view, channel to ask...

>reiser4progs 0.5.4 is from snapshot 2004.04.21-internal.testing.fixed,
>which doesn't look for common people, hence it is not in unstable.

Maybe Namesys should just "release it officially" then. Although it's
pretty much the de facto bug-fixed version. Should be enough to get
it into unstable, imo.

>indeed it is available in debian experimental.
>http://packages.debian.org/reiser4progs

I compiled it myself. It's not difficult to
cp -a ../reiser4progs-0.5.3/debian . and do the rest manually ;)

>really? i still have to finish reading the thread :/
>did Hans really move to GPL?!?

I think I mis-remembered a bit. Or wishful thinking ;)
http://lists.debian.org/debian-legal/2004/05/msg00443.html

"If Debian offers to provide credits in practice but not theory, and 
there is some possibility of getting into a debian installer in the near 
future, then I can probably lose a little and risk a little and put both 
progs and kernel code into GPL V2 for now despite it being a license with  
flaws that beg for fixing."

There is the if in the beginning. I don't know how official this must
be...

http://lists.debian.org/debian-legal/2004/05/msg00456.html
"FWIW, I would like to publicly thank Hans for his decision to release the
whole shebang under a GPLv2 license."

FWIW?
Anyway, I actually bothered to check the README.
"
Reiser4 is hereby licensed under the GNU General Public License version 2.
[...]
The portions of them owned by Hans
Reiser, or authorized to be licensed by him, have been in the past,
and likely will be in the future, licensed to other parties under
other licenses.
[...]
If you interpret
the GPL as not allowing those additional licensing options, you read
it wrongly, and Richard Stallman agrees with me, when carefully read
you can see that those restrictions on additional terms do not apply
to the owner of the copyright, and my interpretation of this shall
govern for this license.
"

But there is the single little catch:
"Finally, nothing in this license shall be interpreted to allow you to
fail to fairly credit me, or to remove my credits such as by creating
a front end that hides my credits from the user or renaming mkfs.reiser4"

I couldn't find any data on the licensing in the reiser4progs sources,
of which I just took a snapshot.

http://namesys.com/legalese.html

That does not take a stance for or against GPL, really...

-- 
mjt




  reply	other threads:[~2004-06-07 20:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03 19:41 reiser4progs 0.5.4 for Debian mjt
2004-06-03 19:58 ` Chris Dukes
2004-06-07 19:33 ` Domenico Andreoli
2004-06-07 20:02   ` mjt [this message]
2004-06-08  9:32     ` Amit Shah
2004-06-08 18:46       ` mjt
2004-06-09  2:28         ` Hubert Chan
2004-06-09  3:46           ` Hans Reiser
2004-06-09 20:36             ` Hubert Chan
2004-06-09 21:50               ` Domenico Andreoli
2004-06-09 21:56                 ` mjt
2004-06-09 23:00                   ` Hubert Chan
2004-06-09 23:06                   ` Domenico Andreoli
2004-06-09  8:08           ` mjt
2004-06-09 20:57             ` Hubert Chan

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=20040607200203.GL4990@nysv.org \
    --to=mjt@nysv.org \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.