Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#31 2013-05-13 22:12:19

Gocom
Developer Emeritus
From: Helsinki, Finland
Registered: 2006-07-14
Posts: 4,533
Website

Re: Check plugin compatibility before upgrading

planeth wrote:

And yes i am not using git but mercurial

Composer uses version control systems to fetch packages from source repositories. To access a git repository you will need git. This is outlined in the installation instructions.

According to Composer’s documentation, for specifically GitHub Composer can fallback to GitHub’s API, if git isn’t installed and the requested repository and version can be fetched using the API. This means that for GitHub, git isn’t required as long as you have a version contrait that is referencing a tag in the repository, and the repository is public. You getting that message, would suggest that either you are trying to require textpattern/lock without a precise version contraint or you are trying to lock it to 4.6.*-dev.

You may also want to check $ composer.phar help [install|update] and the --prefer-dist flag, which overrides Composer to use dist instead of source where possible.

Last edited by Gocom (2013-05-13 22:13:14)

Offline

#32 2013-05-14 08:08:16

planeth
Plugin Author
From: Nantes, France
Registered: 2009-03-19
Posts: 240
Website GitHub Mastodon

Re: Check plugin compatibility before upgrading

Thank you for the explanation.
The whole thing is quite new.
Following your explanation i did give a precise version for the require command : failed again.
using —prefer-dist flag : worked

Though it’s not clear what’s the difference between package source and package dist.

Offline

Board footer

Powered by FluxBB