Use asdf for system packages #173
Conversation
We've talked about this change in the past, checking in the `asdf` configuration file for explicit version management of system dependencies.
|
When we talked about this one, @humitos raised issues about |
| You will need to specify the ``FONTAWESOME_NPM_AUTH_TOKEN`` environment variable | ||
| before installing Node dependenvies. You should be using ``direnv`` locally for | ||
| secret management and encryption. Ask for this token, it's private. | ||
| You will need the following requirements: |
There was a problem hiding this comment.
This change is related to #172, the token is not required because we're using a hosted kit.
There was a problem hiding this comment.
Looks good to me.
It would be good if .tool-versions has a way to specify 3.10.x so, any patch version that you have installed works. Otherwise, we will end up with multiple 3.10 versions installed locally. It's not a problem, of course, just a nice to have 😄
|
Yeah, I wish there was some concept of version selection like that in asdf. There are a few issues, like asdf-vm/asdf#352, that discuss some maybe options, but seems this feature was specifically ruled out. At least with poetry abstracting the Python version a little, it's mostly just wasting the space for each Python core installation, but even a bare installation is about 250MB per install :/ |
We've talked about checking in the
asdfconfiguration file for explicitversion management of system dependencies in the past. This is a lightweight
version of that that gives an explicit way to get started. Using
asdflocallyis out of the scope of documentation here, it's a system level dependency.
📚 Documentation preview 📚: https://read-the-docs-site-community--173.com.readthedocs.build/en/173/