version number issues about composer-repository HOT 5 CLOSED

Oh yeah, composer doesn't like more then four parts.
I'm afraid there is nothing we can do on our side. @riconeitzel and @dsdata need to tag wirh versions using the composer version schema if they want stable versions available.

from composer-repository.

This is not really possible. As you might know, the versioning system for the german language pack is <magento version like 1.7.0.2>. I can't imagine how this should be changed :-(

Why the hell does composer limit the version length!?!

Von unterwegs gesendet.

Am 28.12.2013 um 09:38 schrieb Vinai Kopp [email protected]:

Oh yeah, composer doesn't like more then four parts.
I'm afraid there is nothing we can do on our side. @riconeitzel and @dsdata need to tag wirh versions using the composer version schema if they want stable versions available.

—
Reply to this email directly or view it on GitHub.

from composer-repository.

I've never used them and don't have time right now to look it up, but probably the problem can be solved using composer version aliases.

from composer-repository.

@Schrank if you follow http://semver.org/ you dont need more length.

Internal cause is, composer uses regex to validate/parse versions

from composer-repository.

Yea, I know, but semver doesn't fit our need :-/ Bit thankfully this is Ricos problem in first place :-) I think there are only two ways: change the versioning or fix the composer "bug"

Von unterwegs gesendet.

Am 01.01.2014 um 09:54 schrieb Daniel Fahlke [email protected]:

@Schrank if you follow http://semver.org/ you dont need more length.

Internal cause is, composer uses regex to validate/parse versions

—
Reply to this email directly or view it on GitHub.

from composer-repository.