Replies: 4 comments 2 replies
|
FWIW, edit: this was quickly fixed by jhheider ❤️ |
0 replies
|
I can confirm I'm still unsure if there's a meaningful difference between installing |
0 replies
|
I guess we need to make it clearer there are 2 ways to install all our tools? Is that the confusion? Not sure I understand TBH |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I love pkgx, but since the revamp with pkgm etc. I find myself a bit confused, and I'm lost in GitHub README instructions and instructions at e.g. https://docs.pkgx.sh...
Use case: The simplest solution to stand up ephemeral, reproducible dev environments across a team. Without adding tools globally, and ideally not requiring
sudo.From the docs, I gather I should:
pgkm-brew install pkgxdev/made/pkgmorcurl https://pkgx.sh | shdev-sudo pkgm install devIt seems confusing though that apparently
brew install pkgmalso installpkgx, andcurl https://pkgx.shinstallspkgm?But then I discovered shellcode dev, which seems closer to what I want. But the shellcode solution says to install via brew? So I should uninstall
pkgmand then runbrew install pkgxdev/made/dev, and then perhaps that will maybe also get mepkgx...?In short:
Just trying to understand the intended setup so I can use the tools as designed.
All reactions