[Pkg-octave-devel] octave-pkg-dev and dual builds

Rafael Laboissiere rafael at debian.org
Sat Mar 1 10:06:28 UTC 2008


[resending to the mailing list]

* Thomas Weber <thomas.weber.mail at gmail.com> [2008-02-29 22:34]:

> How do we handle the upcoming Octave 3.1 then?

I have not yet thought about this.

> I mean, octave-pkg-dev can only depend on one of octave3.0 and octave3.1?

Nothing prevents octave-pkg-dev to depend on both.

> Or are we aiming for true dual builds (that is, one source upload produces
> packages for 3.0 and 3.1 at once)?

I think that dual building is the way to go.  We could control this through
a variable in debian/rules, or just infer which octave version to use from
the pacakge name.  In this case, we should make provisions for producing
both octave3.0-pkgname and octave3.1-pkgname packages.  

Also, we have to make a decision regarding the installation directory.
Currently, octave-pkg-dev install *.m files in /usr/share/octave/packages.
Should this path have a versioned name (e.g. /usr/share/octave3.0/packages)?

It is perhaps better if we discuss further about this before uploading the
first package and getting trapped in a wrong naming scheme.

-- 
Rafael




More information about the Pkg-octave-devel mailing list