| 1 |
On Saturday 07 November, Robin H. Johnson wrote: |
| 2 |
|
| 3 |
> On Fri, Nov 06, 2009 at 04:04:41PM -0800, Sébastien Fabbro wrote: |
| 4 |
> > We have a few fetch restricted Intel packages in the main tree (icc, |
| 5 |
> > ifc, mkl, ipp, tbb). All except tbb are closed-source but free with |
| 6 |
> > non-commercial licenses. Lately upstream has repackaged the icc and |
| 7 |
> > ifort (ifc) as a big tar blob containing all of them, but also |
| 8 |
> > release some of them separately. For various reasons we would like |
| 9 |
> > to keep separate ebuilds. The problem is the separate packages have |
| 10 |
> > common libraries, causing duplication and file collisions. So the |
| 11 |
> > idea was to download the tar blob which contain a few binary rpms |
| 12 |
> > and base new ebuilds on these rpms. This means we will have to |
| 13 |
> > re-distribute the rpms on our mirrors. I can't understand from the |
| 14 |
> > many licenses if we are allowed to do it, it surprisingly looks |
| 15 |
> > like we can do it. |
| 16 |
> > |
| 17 |
> > Anyone with better understanding of the licences could help? |
| 18 |
> > Upstream does not answer. |
| 19 |
> Can you list the license files please? I'll poke at them after that. |
| 20 |
> |
| 21 |
|
| 22 |
The one in the tree (Intel-SDP) has slightly changed. New one: |
| 23 |
http://software.intel.com/en-us/articles/intel-software-development-products-license-agreement/ |
| 24 |
|
| 25 |
-- |
| 26 |
Sebastien |
Archives