[Pkg-octave-devel] Epoch in version number of octave2.1

[Rafael Laboissiere]

* Dirk Eddelbuettel <edd at debian.org> [2005-11-26 20:14]:

> On 26 November 2005 at 23:34, Rafael Laboissiere wrote:
> | Second, by restoring the generation of the octave virtual package by
> | octave2.9 and making it depend on octave2.1.
> 
> Clever. But doesn't it require octave2.9 to be installed to get
> octave2.1?

No.

> Or simply 2.9 to be in the archive to produce a package "octave" that
> itself depends on 2.1, so in a way 2.9 pointing to 2.1 and giving users
> 2.1 even if it comes from a 2.9 source.

Yes, this will be the case.  In this scenario, if a user does not have
any octave package installed yet and types "apt-get install octave", then
the octave_2.9.4-n_<arch>.deb file will be downloaded and since this
package will depend on octave2.1, octave2.1_2.1.72-n will be installed.
This is not very elegant, because the user will see something like:

$ dpkg -l octave\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  octave         2.9.4-6        GNU Octave language for numerical computation
ii  octave2.1      2.1.72-7       GNU Octave language for numerical computation

but it will work.

Thanks for your comments.  New uploads of octave2.1 and octave2.9 will
come soon, in the usual faster-than-sound style, err... in the 
faster-than-master.debian.org-MTA style).

-- 
Rafael