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
"../.." is prepended to the path in the xml file after installation #259
Comments
Confirmed. And clearly a bug. |
Ok, let me try to fix it. I'm able to produce a PR tomorrow 😄. |
Correct. We try to behave as closely as possible the way composer works when it comes to version constraints itself. Given that you can, as you did, install a phar without specifying a version, we prepend it with
That is weird, as that should not have any logical relation.
No, certainly not normal behavior. |
I just checked and it seems related to the phar.io/filesystem package and the Because my app installation path is A workaround seems to use the |
Realpath will also resolve symbolic links. That's not helpful in this case. |
You're right about the relativePath resolving though. By default we prepend the working directory to the "tools" path, somehow this gets mangled when receiving the path from the registry. |
Hello !
I'm currently using Phive in some projets and just encountered a strange behaviour.
My version:
Context
I just installed a phar using the simple
install
command :This command results in the following XML configuration :
You can notice that there is a
^
before the version number. This character is familiar when using composer so I though that it means any version after3.5.5
and before3.6.0
.Problem
When I ran the
phive install
command after the XML was generated (for example on my CI environment), the XML get rewritten like this :Each time I ran the
phive install
command it preprend../..
before the location parameter.Workaround
I found that if I remove the
^
I haven't any problem with the path update…Is it a normal behaviour ? If it's a real issue, I can work on a PR to fix it.
The text was updated successfully, but these errors were encountered: