Re: Developing Octave-Forge packages

[Søren Hauberg]

man, 27 12 2010 kl. 11:25 -0600, skrev Jordi Gutiérrez Hermoso:
> 2010/12/27 Søren Hauberg <address@hidden>:
> > man, 27 12 2010 kl. 08:30 -0600, skrev Jordi Gutiérrez Hermoso:
> >> Hi, I started working on Debian bug #607071 yesterday:
> >>
> >>      http://bugs.debian.org/607071
> >
> > For what it's worth, this package seems to work for me (though others
> > are having grave troubles).
> 
> This is very odd. It's probably an API change in GiNac. Which version
> are you using? On Debian we have 1.5.8

I've tried the 1.5.1 that is distributed with Ubuntu and a self-compiled
1.5.8. They seem to work, though I am not a "real" user (only a
debugger) so I'm probably not the best tester out there...

> >> I notice that that Makefile included
> >> with the package does something weird about disabling the compilation
> >> environment once it's been built once. Why?
> >
> > Which makefile is that? I haven't noticed such behaviour of the one in
> > the 'src' directory.
> 
> The one in the package's top level directory. It's got a package
> target that renames the build files in src/ in order to disable them.
> Is this unusual for a 'Forge package?

I haven't seen such a behaviour, but honestly I haven't spend too much
time on the build system.

> Another question, how do you generate a tarball from the svn sources?
> I couldn't figure it out at first glance. Lots of maintainer scripts
> all around, didn't know which one to call.

Basically, it should be fine to do a

  svn export $packagename $packagename-$packageversion
  cd $packagename-$packageversion/src; ./autogen.sh; cd ../..

and then tar up the directory. I think all the maintainer scripts are
from the old monolithic times.

Søren