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

[Rafael Laboissiere]

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

> Yes, but if we had only one octave-audio source package (building two
> octave3.0-audio and octave3.1-audio), we would need to disable the
> octave3.0 build at some point (or using different source packages).
> 
> So, I'm for avoiding dual builds.

Okay, let us continue with our current plan and address the 3.0 vs. 3.1 and
dual-build issues later.

> Eh, I don't think we will be able to handle -forge packages for both 3.0
> and 3.1. Forge consists of 40+ packages, already increasing our package
> number by a *factor* of 5. Doubling this again with a 3.0 and 3.1
> diversion is out of the question.

I was thinking about doing things automatically, but I guess you are right,
this would represent too much work for us.  We could maintain the -forge
packages only for the recommended version of Octave (3.0 now) and let the
users use pkg.m for the development version (3.1 in the future).

> By the way, our mass ITP has started a massive discussion about
> packaging everything under the sun on debian-devel.

I haven't seen the thread yet.  Anyway, I am not worried about this.  I
vaguely remember that ten years ago, when I joined Debian, there was a huge
discussion about the number of packages reaching 1000.  Some apocalypse
DD-prophets would predict the collapse of Debian when this number would be
reached.  Well, the project survived, apparently.

-- 
Rafael