octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pending interval-3.0.0 release


From: Oliver Heimlich
Subject: Re: pending interval-3.0.0 release
Date: Sun, 20 Aug 2017 11:00:41 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

On 19.08.2017 18:48, Oliver Heimlich wrote:
> On 19.08.2017 18:32, Olaf Till wrote:
>> Oliver,
>>
>> trying to rebuild the release I get stuck with that:
>>
>> git clone https://github.com/oheim/ITF1788.git "build/ITF1788"
>> Cloning into 'build/ITF1788'...
> ...
>> Compiling src/test/abs_rev.itl ...
>> Traceback (most recent call last):
>>   File "/usr/lib/python3.4/runpy.py", line 170, in _run_module_as_main
>>     "__main__", mod_spec)
>>   File "/usr/lib/python3.4/runpy.py", line 85, in _run_code
>>     exec(code, run_globals)
>>   File 
>> "/home/olaf/devel/octave-forge/package-repositories/all/octave-forge/interval/build/ITF1788/itf1788/__main__.py",
>>  line 27, in <module>
>>     from . import dslparser
>>   File 
>> "/home/olaf/devel/octave-forge/package-repositories/all/octave-forge/interval/build/ITF1788/itf1788/dslparser.py",
>>  line 29, in <module>
>>     import ply.lex as lex
>> ImportError: No module named 'ply'
> 
> you will need to install the python modules listed at the end of this file.
> https://github.com/oheim/ITF1788/blob/master/setup.py
> 
>> I admit I'm somehow not happy with requiring to clone a 'non standard'
>> external repo for package building. Is there no other solution? What
>> is this python code supposed to do in building the interval package?
> 
> I am also not satisfied with the current solution and am open to better
> alternatives.  Would it be better to copy the python code into a
> bootstrap folder of the Octave package repository?
> 
> The python code is used to convert the src/test/*.itl files into Octave
> code, which will then be run and produce the file inst/test/itl.mat,
> which contains the test data from the itl files.
> 
> The code generation requires the python code, which is developed at
> Github, and depends on python and some python modules.
> 
> If you want to skip that part of the reproduction, you could use the
> itl.mat from the tarball, which I have prepared for the release tracker.

I have now put the generated test data under version control and it is
possible to run the package from source or make a release tarball
without these special dependencies.

https://sourceforge.net/p/octave/interval/ci/43284e87a6eb8e80c9a8cbc2f0cb3b07136380af/

Oliver




reply via email to

[Prev in Thread] Current Thread [Next in Thread]