You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pkgx install should uninstall if previously installed and then install again the new version. Just like sudo apt-get install docker-ce-cli=5:25.0.3-1~ubuntu.22.04~jammy.
If 1 is too hard to be implemented, the least pkgx should do is to return a non-zero code when another version of the package is already installed.
This happened in my CI/CD, where I ship an environment with pkgx install java@17, but some services needed to use java@11.
Their pipelines were configured to run pkgx install java@11 but since a succesful exit code was given, the application was still being built with java@17.
The text was updated successfully, but these errors were encountered:
felipecrs
changed the title
pkgx install should overwrite existing versionspkgx install should overwrite existing versions
Apr 24, 2024
as far as your CI/CD goes, even something as simple as: rm -r ~/.local/bin || true should be sufficient, if you need to use the install functionality, rather than either an environment or shebang-style invocation.
as far as your CI/CD goes, even something as simple as: rm -r ~/.local/bin || true should be sufficient, if you need to use the install functionality, rather than either an environment or shebang-style invocation.
Yeah. For now I do pkgx uninstall java before pkgx install.
Let's say I previously had:
pkgx install java@17
Then later:
Here is what I think:
pkgx install
should uninstall if previously installed and then install again the new version. Just likesudo apt-get install docker-ce-cli=5:25.0.3-1~ubuntu.22.04~jammy
.If 1 is too hard to be implemented, the least pkgx should do is to return a non-zero code when another version of the package is already installed.
This happened in my CI/CD, where I ship an environment with
pkgx install java@17
, but some services needed to usejava@11
.Their pipelines were configured to run
pkgx install java@11
but since a succesful exit code was given, the application was still being built with java@17.The text was updated successfully, but these errors were encountered: