From: "Sébastien Fabbro" <bicatali@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] redistribute intel rpms
Date: Fri, 6 Nov 2009 16:45:23 -0800 [thread overview]
Message-ID: <20091106164523.397b9800@canfar.phys.uvic.ca> (raw)
In-Reply-To: <robbat2-20091107T002817-593206750Z@orbis-terrarum.net>
On Saturday 07 November, Robin H. Johnson wrote:
> On Fri, Nov 06, 2009 at 04:04:41PM -0800, Sébastien Fabbro wrote:
> > We have a few fetch restricted Intel packages in the main tree (icc,
> > ifc, mkl, ipp, tbb). All except tbb are closed-source but free with
> > non-commercial licenses. Lately upstream has repackaged the icc and
> > ifort (ifc) as a big tar blob containing all of them, but also
> > release some of them separately. For various reasons we would like
> > to keep separate ebuilds. The problem is the separate packages have
> > common libraries, causing duplication and file collisions. So the
> > idea was to download the tar blob which contain a few binary rpms
> > and base new ebuilds on these rpms. This means we will have to
> > re-distribute the rpms on our mirrors. I can't understand from the
> > many licenses if we are allowed to do it, it surprisingly looks
> > like we can do it.
> >
> > Anyone with better understanding of the licences could help?
> > Upstream does not answer.
> Can you list the license files please? I'll poke at them after that.
>
The one in the tree (Intel-SDP) has slightly changed. New one:
http://software.intel.com/en-us/articles/intel-software-development-products-license-agreement/
--
Sebastien
next prev parent reply other threads:[~2009-11-07 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-07 0:04 [gentoo-dev] redistribute intel rpms Sébastien Fabbro
2009-11-07 0:28 ` Robin H. Johnson
2009-11-07 0:45 ` Sébastien Fabbro [this message]
2009-11-07 1:16 ` Robin H. Johnson
2009-11-07 1:58 ` Sébastien Fabbro
2009-11-12 7:54 ` Robin H. Johnson
2009-11-13 20:20 ` Sébastien Fabbro
2009-11-07 8:28 ` [gentoo-dev] " Duncan
2009-11-12 6:55 ` Sébastien Fabbro
2009-11-12 10:16 ` Duncan
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=20091106164523.397b9800@canfar.phys.uvic.ca \
--to=bicatali@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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