public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	tziporet Koren
	<tziporet-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
Subject: Re: ibutils license problems + a few other minor issues
Date: Tue, 23 Feb 2010 19:01:29 +0200	[thread overview]
Message-ID: <4B8409E9.2060608@dev.mellanox.co.il> (raw)
In-Reply-To: <4B743A4A.90004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Doug,

Thanks for reviewing this.
All the licensing issues have been fixed. See below.

On 11/Feb/10 19:11, Doug Ledford wrote:
> The ibutils tarball as found for download on the openfabrics web site
> has some licensing issues that need resolved ASAP.  The tarball in its
> current form is probably illegal to distribute until the items are
> fixed.  So, here's what popped up in review (done by Jay Fenlason):
>
> The COPYING files sprinkled around in the tarball are not consistent.
> Some of them contain a copy of the GPLv2, some of them contain a
> statement that the package is licensed under either GPLv2 in the file
> COPYING or the OFA BSD license included here in.

Fixed - it's consistent now

> Of course, it doesn't
> work to reference a COPYING file from within the COPYING file you are
> referencing and say it has the information you aren't including here.  I
> would suggest that the proper place for the statement of GPLv2 or BSD is
> in possibly a LICENSE file with the COPYING file being the GPLv2 as
> stated.  It also seems redundant to have multiple COPYING files and
> possibly also multiple LICENSE files in a single tarball, so cleanup of
> unnecessary files seems in order here.

Fixed - there is one COPYING file at the root of the tree, and all
the (c) headers are referencing to this COPYING file.

> There are a number of files who have headers that indicate they are
> *not* under either GPLv2 or BSD.
>
> ibdm/replace/regex.[ch] are LGPLv2+, so need a LGPLv2+ COPYING somewhere

I don't see LGPL in these files, only GPL. It says "GNU *Library*
General Public License", so this could be the reason for confusion.

> ibdm/replace/{memset.c,realloc.c,malloc.c} are GPLv2+ versus GPLv2

So basically, we have the whole ibdm/replace/ directory under
GPLv2+ license. I described it in the COPYING at the tree root.

> ibdm/src/fabric_sim.cpp claims to be confidential and proprietary! It
> refers to LICENSE.txt for t&c. There is no LICENSE.txt under ibdm/.
> There is one under ibmtsim/utils/ though.

Fixed - they are all GPLv2 or BSD, and they are all referencing to
the same COPYING file.
  
> ibmgtsim/config/{missing,config.sub,ltmain.sh,depcomp,config.guess}
> is GPLv2+
> ibmgtsim/config/install-sh is X license
>
> ibmgtsim/utils/{,un}install.sh is GPLv2+

These files are generated by things like autotools or m4.
They are not part of the git tree, but they do exist in the
tarball, because tarball is created after autogen.sh execution.

-- Yevgeny
  
> There are also a few other minor issues with the tarball as it builds:
>
> /usr/bin/ibnlparse has no man page
>
> /usr/share/man/man1/ibdm-ibnl-file.1.gz
> /usr/share/man/man1/ibdm-topo-file.1.gz
> Are in man1, but have no corresponding executables. Perhaps
> they should be in a different man section?
>

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-02-23 17:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 17:11 ibutils license problems + a few other minor issues Doug Ledford
     [not found] ` <4B743A4A.90004-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-02-15 20:50   ` Tziporet Koren
2010-02-23 17:01   ` Yevgeny Kliteynik [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=4B8409E9.2060608@dev.mellanox.co.il \
    --to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=tziporet-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox