#763052 Composer: Handle stability flags in version constraints

#763052#5
Date:
2014-09-27 14:52:14 UTC
From:
To:
Hi,

php-doctrine-annotations used to depend on php-doctrine-lexer (>= 1~),
and is now depending on php-doctrine-lexer (>= 1), generated from
composer.json that contains "doctrine/lexer": "1.*" in require.

Not sure if that’s intended: if not, it’s a bug worth fixing.

It may be intended, since versions are likely to be 1.$something~~$else
at worse, and thus (>= 1) will be higher, bat using (>= 1~) or even
(>= 1~~) may be safer. Feel free to close this issue anyway if that was
intended since the safer view may well be pointless.

Regards

David

#763052#12
Date:
2014-09-29 12:14:53 UTC
From:
To:
2014-09-27 16:52 GMT+02:00 David Prévot <taffit@debian.org>:

Hi David,

The current (new) behavior is mostly correct.
stable (which is the default).

Leaving this bug open for the remaining dev, alpha, beta, RC
minimum-stability or stability flag.

Note that we won't be able to match composer completely:
- with composer: >=1.1@stable will not match 1.2dev.
- with dpkg: >=1.1 will match 1.2~~dev

Regards