Re: A new way to specify versionned dependencies may be needed
On Fri, Oct 03, 2003 at 09:19:39AM +0200, Dagfinn Ilmari Mannsåker wrote:
> > So I'd like my package to conflict with versions A to B of foo. I tried
> > to specify it with "Conflicts: foo (>> A), foo (<< B)" but, as I feared,
> > it does not work since it now conflicts both with all versions >> A and
> > with all versions << B (as A << B, that means all versions).
> How about "Depends: foo (<< A) | foo (>> B)"?
No, my package does not depend in any way on foo. Depending on foo only
to prevent a few specific versions of foo to be installed would be evil,
> > Currently, there's no need for such a feature for positive dependencies
> > (Depends, Recommends and Suggests), because there is a workaround:
> > "Depends: foo (>> A), foo (<< B)" works for "Depends: foo (>> A, << B)",
> > but it only works because only one version of foo can be installed at a
> > time. If versionned provides are ever implemented, it may become
> > possible to have several versions of a package at a time, thus breaking
> > this workaround.
> The above will also break if versioned provides are implemented.
Which "The abobe"? Your "Depends: foo (<< A) | foo (>> B)"? Or my
"Depends: foo (>> A, << B)"? I can't see why mine would be broken. Did I