[Pkg-octave-devel] Versioning the dependency on octave for the OF packages

[Sébastien Villemot]

Jordi Gutiérrez Hermoso <jordigh at octave.org> writes:

> On 9 March 2012 16:32, Thomas Weber <tweber at debian.org> wrote:
>> On Fri, Mar 09, 2012 at 09:32:58PM +0100, Sébastien Villemot wrote:
>>> Also, for future improvements to octave-pkg-dev, we may want to exploit
>>> the dependency versioning that is in the DESCRIPTION file of Forge
>>> packages. Ideally octave-pkg-dev should fail if the installed octave is
>>> lower than the required one. For instance, such a mechanism would have
>>> prevented #649395; see also #661123 for a similar problem, but in that
>>> case upstream also forgot to tighten the dependency.
>>>
>>> It would also be useful to exploit the dependency versioning between
>>> Forge packages, for similar reasons.
>>
>> This might make it difficult to upload new versions of packages. Yes,
>> textread is missing in the io package - do we really want to prevent an
>> update of octave-io due to this?
>
> I'm not really following. Is there something we should be fixing in
> the upstream package? Add a dependency? Just say the word...

It’s a Debian specific issue: basically we uploaded a version of io too
recent for octave 3.2. See #649395 as mentionned in my previous email.

-- 
Sébastien Villemot
Researcher in Economics & Debian Maintainer
http://www.dynare.org/sebastien
Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-octave-devel/attachments/20120309/1b8236ad/attachment.pgp>