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

[Thomas Weber]

On 01/03/08 11:06 +0100, Rafael Laboissiere wrote:
> > 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.

Well, if both are installed, we can't take the easy way of just calling
"octave" in the shell and knowing which version it will be.

> > 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. 

I'm not so sure. Looking at the history of 2.1 and 2.9, from a certain
point on onwards it was only possible to build with 2.9. 

> 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.

I don't think there needs to be lots of discussion. If we indeed need a
new naming scheme, dpkg will remove the files from the old paths and the
new deb packages will install into the new path.

So, from the installation part, I don't see much of a problem.

	Thomas