Navigation Menu

Skip to content
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

fixed composer.json to download the same set of vendors as with use of c... #6043

Merged
merged 1 commit into from Aug 23, 2014

Conversation

mgazdzik
Copy link
Contributor

...omposer.lock. that way Piwik can be also installed with Composer as dependency along with its dependencies.

Originally this issue came out when I tried to download Piwik along with it's plugins using different composer.json file. That way Composer would download dependencies described in composer.json. This caused installation and Piwik in general to break down due to vendor version mismatch. In 'standard' use case on the other hand it worked well, as strict version was stored inside of composer.lock file.

Tilde operator is not quite safe for precise version marking (ref. https://getcomposer.org/doc/01-basic-usage.md#next-significant-release-tilde-operator- ) , so I would propose to always keep composer.json and composer.lock up-to-date using precise versioning in composer.json, so Piwik can be managed with Composer easily.

For now I have found that lessphp was causing problems after download, but it generally could be a good idea to switch to strict versioning for all vendors.

…f composer.lock. that way Piwik can be also installed with Composer as dependency along with its dependencies
@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 76a0be7 on mgazdzik:fixComposerJson into 0610a6d on piwik:master.

@mattab
Copy link
Member

mattab commented Aug 23, 2014

This caused installation and Piwik in general to break down due to vendor version mismatch.

@mgazdzik I think that when there is a new version of twig or leafo etc. from our composer.json, then this problem will re-occur again that there could be mismatch between the downloaded version (when including Piwik as composer dependency) and the one specified in composer.lock

So i'm not sure if this will fix future problems but anyway +1 for mering this PR as it is.

mattab pushed a commit that referenced this pull request Aug 23, 2014
fixed composer.json to download the same set of vendors as with use of c...
@mattab mattab merged commit 4af9ce9 into matomo-org:master Aug 23, 2014
@mgazdzik
Copy link
Contributor Author

I think that if all vendors would be defined with strict versioning in both - composer.lock (which is by defaul) and in composer.json (which I'm hoping can be introduced) we shouldn't ever have this problem again. After there is some change in any vendor that we want to introduce - simply put it in composer.jsom first, and then refresh composer.lock using "composer update". This way both files will contain the same version tag and will point to the same commit.

@mattab
Copy link
Member

mattab commented Aug 23, 2014

@mgazdzik ok that makes sense I think!

Could you create issue to keep track of this request?

@mgazdzik mgazdzik deleted the fixComposerJson branch August 25, 2014 07:35
@mgazdzik
Copy link
Contributor Author

@mattab - sure, just created it - #6058 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants