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

[Sébastien Villemot]

Thomas Weber <tweber at debian.org> writes:

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

My guess is that if upstream tightens the dependency, it is for a
reason. In the case of octave-io it was justified from my POV.

But if you think a FTBFS is too restrictive, we could at least have a
big fat warning, and let the developer decide whether to override it or
not.

-- 
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/b641d19f/attachment.pgp>