Replies: 4 comments 2 replies
-
FWIW, edit: this was quickly fixed by jhheider ❤️ |
Beta Was this translation helpful? Give feedback.
-
I can confirm I'm still unsure if there's a meaningful difference between installing |
Beta Was this translation helpful? Give feedback.
-
Closing in favor of asking in Discord. |
Beta Was this translation helpful? Give feedback.
-
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 |
Beta Was this translation helpful? Give feedback.
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/pkgm
orcurl https://pkgx.sh | sh
dev
-sudo pkgm install dev
It seems confusing though that apparently
brew install pkgm
also installpkgx
, andcurl https://pkgx.sh
installspkgm
?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
pkgm
and 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.
Beta Was this translation helpful? Give feedback.
All reactions