[Pkg-octave-devel] Binary MEX files in octave-nan upstream tarball

[Sébastien Villemot]

Jordi Gutiérrez Hermoso <jordigh at octave.org> writes:

> 2011/9/27 Sébastien Villemot <sebastien.villemot at ens.fr>:
>> I have a question concerning the upstream tarball: it contains binary
>> MEX files which must have been compiled with MATLAB by the upstream
>> maintainer (this affects the current 2.4.1 tarball and the new 2.4.4
>> tarball).
>>
>> I am wondering if this is DFSG/policy-compliant, or if we need to
>> repackage the upstream tarball without these binary blobs.
>
> It's not a DFSG violation. The source is there, and if you have
> Matlab, you can recompile them and modify them. Up to you to repackage
> the source tarball, but I don't see a reason to do so if it's more
> trouble.

Ok, thanks for the clarification. I will then go ahead with the pristine
tarball.

-- 
Sébastien Villemot
Researcher in Economics at CEPREMAP & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-49-90 - GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20110927/48f4f313/attachment.pgp>