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

Re: Help packaging an octave toolbox



On 6/12/20 1:27 AM, Rafael Laboissière wrote:
The octave-gdf package does not use the Octave's pkg mechanism.  Its functions are immediately available upon the installation of the package in the Debian system, without need of running "pkg load":

    $ sudo apt install octave-gdf
    $ echo "which gdf_reader" | octave-cli -q
    'gdf_reader' is a function from the file /usr/lib/x86_64-linux-gnu/octave/site/oct/x86_64-pc-linux-gnu/gdf/gdf_reader.mex

This is the reason it does not appear in "pkg list" neither.

So, I think it does not make much sense to create INDEX/DESCRIPTION files for your octave-zmat package if you are not going down the road of installing it though the pkg mechanism.  This is essentially what is done for the Octave-Forge packages, which use the functionalities provided by the dh-octave at build time.


that makes perfect sense. I just tested the generated deb file, the installed function is ready to be used without needing pkg, so it is actually a better way to go.



The ideal situation would be to adapt the upstream source for using the pkg mechanism:

https://octave.org/doc/v4.2.1/Creating-Packages.html#Creating-Packages


as mentioned above, I am convinced that the way that libgdf installs the mex function is a better way than pkg, and I will stay this way.

thanks a lot!

Qianqian



Best,

Rafael Laboissière


Reply to: