phive
phive copied to clipboard
phar-io
Add support to specify a stablity (stable, alpha, beta, ...)
Upgrading from a stable 1.0.0 to 2.0.0-alpha.1 may or may not be desired. We should make sure that a user can request a certain stability level when installing or upgrading.
I think the problem which this issue is about is currently happening "live": our pipelines started breaking last week because phive is used to install php-cs-fixer, which has released version v3.0.0-beta.1, which fails for us with PHP Fatal error: Uncaught Error: Call to undefined method PhpCsFixer\Config::create()
While I understand that to be a problem in general, I'm not sure I understand why this problem occured for your CI pipeline: Usually, on CI, "phive install" is used to re-create a predefined set of tools and their respective versions as recorded in either phive.xml or .phive/phars.xml.
So unless php-cs-fixer in 3.0.0-beta.1 works for you locally, I don't see how it would end up being installed on CI?
I don't see how it would end up being installed on CI?
Don't even ask :-D It's something that I am pushing to fix, but atm the CI QA containers are built differently than the ones used by developers, and they are not even available during development so that we could troubleshoot them locally :-O.
Do you need help fixing it? I suggest replacing phar-io/version with surely working correctly composer/semver.
Then what? Write what the matter is, maybe someone will send you a PR with a solution. This zero activity in this code repository does not indicate that the problem is going to be resolved anytime soon.
The title as well as the description already contain everything: Phive lacks a means to SPECIFY a stability when installing.
If I understand correctly, cannot specify stability when invoking the install command?
Can't you just force the installation of only stable versions? As long as the current issue is unresolved?
This issue is about an enhancement. It's not a real technical issue stopping anyone from using phive. I thus do not see a need for a hack like that.
And this is not a very complex issue. We just need to implement it but there are more important things to be done first. Feel free to have a look at it.
This issue is about an enhancement. It's not a real technical issue stopping anyone from using
phive. I thus do not see a need for a hack like that.
I came here because I wanted to report a bug. However, I found #333 before that. Issue was closed as it was supposed to be a copy of #154. Now you write that this is a thread for an improvement, and there are no complications in the operation of the application. There is a complication because I have to quite accurately determine what version of composer I want to install, otherwise the RC version is installed. This is a bug.
Suppose I have 10 applications that I want to install and every time I install them I have to go to the repository for each one and make sure what the latest version is, which is not alpha, beta, rc. So why do I need a tool like Phive when I have to check everything myself?
Phive helps you to manage dependcies. It doesn't free you from thinking of what you're doing.
Even if phive had the missing feature, you still would need to know when to update what and what side effects that may have.
I'm not arguing against implementing this, just that it's not a show stopper.