Re: Unmaintained packages - becoming a maintainer?

[Julien Bect]

Le 27/05/2015 07:15, address@hidden a écrit :
> > 1) In your post "Octave Packages CI build dependencies
> > <http://neilhopcroft.com/octave-packages-ci-build-dependencies/>", you
> > report "Build error" for stk, but you don't provide the version of stk
> > (nor the version of Octave) that you have tested. Could you please tell
> > me more about this "Build error"? A release was made very recently
> > (2.3.0), could you try it and see if the build error is still there?
> I have put a little explanation of the build error I see in stk here:
>
> http://neilhopcroft.com/build-errors-in-the-stk-octave-package/
>
> ...in summary, it installs differently to the other packages and I wasn't
> doing it right. Would it be difficult to make it behave similarly to other
> packages as far as package management is concerned?
>
> Neil

Ok, I understand now. Thanks for your feedback.

You're getting the source files from Mercurial, not from a release of 
stk as an octave package. The Mercurial sources is not equivalent to an 
unpacked octave package tarball, which explains why the rest of your 
process doesn't work. The reason for this is that stk is also released 
as an "all purpose" package that can also be used from Matlab (and 
therefore doesn't rely on the octage pkg mechanism).

You're right about the README file at the root of the source tree: it 
only explains how to use stk "in place", not how to install it as an 
octave package. I have to fix this.

If you want to create an octave package from the mercurial sources, you 
just have to type "make octaveforge-release" at the root (or just "make" 
but then you'll get other things that you don't need). Then you'll find 
the package (both unpacked and packed as a tarball) in build/octaveforge.

@++
Julien