[Pkg-octave-devel] Regarding octave-interval packaging

[Oliver Heimlich]

Am 25. April 2016 00:43:17 MESZ, schrieb "Rafael Laboissière" <rafael at laboissiere.net>:
>* Oliver Heimlich <oheim at posteo.de> [2016-04-24 22:39]:
>
>> Am 24. April 2016 15:41:03 MESZ, schrieb "Rafael Laboissière"
><rafael at laboissiere.net>:
>>> * Oliver Heimlich <oheim at posteo.de> [2016-04-24 11:39]:
>>>
>>>> 3. I want to split the package into an arch-independent package and
>
>>>> an arch-dependent package, since 90% of the package goes into 
>>>> /usr/share as Lintian says. I still have to figure out the correct 
>>>> dependencies between the packages.
>>>>
>>>> [snip]
>>>
>>> We have already discussed on this issue, and we decided to not split
>
>>> the arch-dep and arch-indep packages:
>>>
>>>
>http://lists.alioth.debian.org/pipermail/pkg-octave-devel/2015-October/011775.html
>>
>> The uncompressed package is clearly beyond the 2MB limit (although I 
>> could reduce it by stripping some test files).
>
>The message in October 2015 regarded version 1.2.0-1 of the 
>octave-interval package.  I did not realize that the situation for
>1.4.1 
>may have changed.  At any rate, once you strip the test files, does the
>
>package still have more than 2Mb in /usr/share?
>
>Rafael
>
>_______________________________________________
>Pkg-octave-devel mailing list
>Pkg-octave-devel at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-octave-devel

Okay, in release 1.3.0 some lengthy m-file functions and examples with images have been added to the manual. The current git revision would end up with (uncompressed) 3.1MB in /usr/share. After the upcoming 1.4.2 upstream you can aproximately add another 500kb.

Also many of the images for the manual have to be generated from m-file scripts, which takes a significant amount of time. And it's going to take even longer in the upcoming 1.4.2 upstream.

I don't know how the Debian build system works. Would it be able to produce only arch-dependent packages for most platforms? Then it would be possible to save a lot of build time as well.

Oliver