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

Rafael Laboissiere rafael at debian.org
Sun Mar 2 14:55:47 UTC 2008


* Thomas Weber <thomas.weber.mail at gmail.com> [2008-03-02 10:43]:

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

For that reason, octave-pkg-dev uses currently "octave3.0" when calling the
Octave program for installing the pkg.

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

Yes, you are right.  This is the reason why we had separate octave2.1-forge
and octave2.9-forge upstream tarballs.

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

I was also thinking about the pacakge naming scheme.  Should we call all the
octave-forge packages octave3.0-something now?

-- 
Rafael



More information about the Pkg-octave-devel mailing list