-
-
Notifications
You must be signed in to change notification settings - Fork 156
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install google-closure-compiler #185
Comments
Should be fixed once composer/semver#48 is merged |
As you can read in composer/composer#6129 this is unlikely to happen. Could you probably implement some way of "translating" the version numbers? Composer limits the number of digits to 6. So, e.g. making it the days since epoch (would be 17303 today) should be sufficient for a few decades. For the record: I also opened google/closure-compiler-js#55 to ask them to change the versioning scheme. |
Translation would involve too many things, not sure this is a way anyone wants to go into. The best thing I can imagine here is to allow at least exact versions matching, while ignoring everything else. Yes, we might miss some patch versions in this case, but at least we'll have package installed. |
Whatever it is, what's needed to fix this issue. But it seems it's up to you to implement something in the plugin since Composer is of the opinion that "640K ought to be enough for anybody". |
I'm not familiar enough with this plugin to implement it quickly, but I'll try at some point, hopefully, soon. |
The version converter tests are here. |
As a quickhack™, I added these lines to the if (preg_match('/^\d{7,}\./', $version)) {
// composer can only handle 6 digits, convert somehow
// cut off least significant digits
$version = substr($version, -6);
} This is, at least, makes Composer usable for me again. |
Composer is unable to install google-closure-compiler package with the composer-asset-plugin due to a version number parsing issue. I found the actual issue to be in Composer's SemVer component, but it seems they're reluctant to change it (see composer/semver#32). So here goes in case there's something that could be done in composer-asset-plugin to remedy the issue.
Here's a minimal composer.json to reproduce the problem:
composer -vvv update output:
The text was updated successfully, but these errors were encountered: