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

[Jordi Gutiérrez Hermoso]

2011/9/27 Sébastien Villemot <sebastien.villemot at ens.fr>:
> 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.

Oh, I forgot to say, the .deb shouldn't contain binaries that can't be
compiled by Debian. I think what makes sense is to do normal
distribution of the files compiled by Octave but not modify the source
tarball.

- Jordi G. H.