Add metadata for roave/backward-compatibility-check

[sebastianbergmann]

This makes it possible to install Roave/BackwardCompatibilityCheck using Phive.

[sebastianbergmann]

CC @asgrim @Ocramius

[theseer]

Is that really the alias you want to have? ;-)

[theseer]

And, to nit-pick on the wording: you can install it without an alias if you use github releases...

[theseer]

There's not signature for the release phar.
We only support aliases for signed releases.

[sebastianbergmann]

I made the changes proposed here locally in my ~/.phive/repositories.xml. Then phive install --force-accept-unsigned backward-compatibility-check worked.

Feel free to close this pull request if I did something wrong. I just want to be able to install/update the PHAR of roave/backward-compatibility-check using Phive.

[theseer]

You didn't do anything wrong. It technically works just fine.

It's a political decision to not (publicly) allow aliases for unsigned releases.

[sebastianbergmann]

I just realized that an alias (aka. addition to repositories.xml) is not required:

$ phive install Roave/BackwardCompatibilityCheck                        
Phive 0.14.2 - Copyright (C) 2015-2020 by Arne Blankerts, Sebastian Heuer and Contributors
Downloading https://api.github.com/rate_limit
[WARNING]  roave/backwardcompatibilitycheck 4.4.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 4.3.0: No downloadable PHAR 
[WARNING]  roave/backwardcompatibilitycheck 4.2.1: No downloadable PHAR 
[WARNING]  roave/backwardcompatibilitycheck 4.2.0: No downloadable PHAR 
[WARNING]  roave/backwardcompatibilitycheck 4.1.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 4.0.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 3.0.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 2.1.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 2.0.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 1.1.1: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 1.1.0: No GPG Signature 
[WARNING]  roave/backwardcompatibilitycheck 1.0.3: No downloadable PHAR 
[WARNING]  roave/backwardcompatibilitycheck 1.0.2: No downloadable PHAR 
[WARNING]  roave/backwardcompatibilitycheck 1.0.1: No downloadable PHAR 
[WARNING]  roave/backwardcompatibilitycheck 1.0.0: No downloadable PHAR 
[ERROR]    No matching release found! 

$ phive install --force-accept-unsigned Roave/BackwardCompatibilityCheck
Phive 0.14.2 - Copyright (C) 2015-2020 by Arne Blankerts, Sebastian Heuer and Contributors
Downloading https://api.github.com/rate_limit
Downloading https://github.com/Roave/BackwardCompatibilityCheck/releases/download/4.4.0/roave-backward-compatibility-check.phar
[ERROR]    Cannot write phar to /home/sb/.phive/phars/roave 

I will close this pull request now, sorry for the noise. However, Cannot write phar to /home/sb/.phive/phars/roave looks like a bug to me.

[Ocramius]

LGTM, but I don't know what aliases are in phive 🤷

[sebastianbergmann]

@Ocramius The only thing you need to worry about is Roave/BackwardCompatibilityCheck#244 😄

[theseer]

It's a means to support a) short names (like, say, phpdoc rather than having to use phpdocumentor/phpdocumentor) when installing and b) allow non-standard locations to get phars from (phpunit to get it from phar.phpunit.de)

[theseer]

[ERROR] Cannot write phar to /home/sb/.phive/phars/roave

I will close this pull request now, sorry for the noise. However, `Cannot write phar to /home/sb/.phive/phars/roave` looks like a bug to me.

You want to upgrade to 0.14.4. That was bug phar-io/phive#262