-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Support to install with PHIVE #264
Comments
It should already be possible, you need to give the full URL. Adding an alias would make it easier but it requires to sign the PHAR which I'm not sure to want to do yet. |
It doesn't work because of PHIVE bug with pre-release suffixes in version constraints. See phar-io/phive#145 for details. |
Bug with pre-release suffixes in version constraints is now fixed, but installation without signed PHAR still You should sign the PHAR, if not earlier, when a stable box 3.0 version comes on. $ sudo phive install -g https://github.com/humbug/box/releases/download/3.0.0-beta.4/box.phar
Phive 0.11.0 - Copyright (C) 2015-2018 by Arne Blankerts, Sebastian Heuer and Contributors
Downloading https://github.com/humbug/box/releases/download/3.0.0-beta.4/box.phar
[ERROR] Failed to download load https://github.com/humbug/box/releases/download/3.0.0-beta.4/box.phar.asc: HTTP Code 404 |
As things stand right now I'm not leaning towards signing my PHARs and more on the contrary remove the OpenSSL signature. I'm still waiting on a conservation or two with a couple more people more knowledgeable than me about security to make up my mind, but for now I only see downsides to signing a PHAR. In any case PHIVE should work without signed PHAR IMO which is the direction taken from what I see in the issue you linked (phar-io/phive#134). |
- Fix broken links - Add missing elements in the Readme ToC - Add installation instructions with Phive Closes #264
@theofidry After 2 years phive works :)
Please reconsider
What an easy way! |
Add support to install Box with PHIVE.
The text was updated successfully, but these errors were encountered: