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
Originally posted by iilyak December 30, 2022
Some of the packages require setting of environment variables to make them work. For example golang require GOPATH (for old versions of go), java require JAVA_PATH. I set environment variables in .envrc (and use https://direnv.net/ to load them).
For Java specifically I have following line.
export JAVA_HOME=$(dirname $(dirname $(expand_path $(aqua which java) "/")))
My concern is that the user of the package need to know the layout of the package.
The idea is to let aqua define a dictionary and have a mechanism to get values from dictionary.
Currently aqua doesn't care about fields it doesn't know about. So I changed the registry.yaml as described above and used https://github.com/TomWright/dasel to extract the values.
Unfortunately, we don't work on this proposal soon, because
aqua should be simple and easy to use so that we can introduce aqua in your teams, projects, and organizations easily. New users should be able to use aqua without high learning cost. So we should be careful to add new commands and increase the learning cost
Currently, we are working on another issues so we don't have enough time to consider this proposal
This feature is unneeded for almost packages, so the priority is low
On the other hand, this proposal is interesting so we'll consider when we have a time.
We have to design simple user interface.
Discussed in https://github.com/orgs/aquaproj/discussions/1496
Originally posted by iilyak December 30, 2022
Some of the packages require setting of environment variables to make them work. For example golang require GOPATH (for old versions of go), java require JAVA_PATH. I set environment variables in
.envrc
(and use https://direnv.net/ to load them).For Java specifically I have following line.
My concern is that the user of the package need to know the layout of the package.
The idea is to let aqua define a dictionary and have a mechanism to get values from dictionary.
Currently aqua doesn't care about fields it doesn't know about. So I changed the
registry.yaml
as described above and used https://github.com/TomWright/dasel to extract the values.This doesn't solve my problem for two reasons.
dasel
the user need to know the structure of registry.yaml.I am thinking about the possibility of a query mechanism in the aqua itself.
Then I can use the following in my
.envrc
I can also use it to set variables in fish:
The text was updated successfully, but these errors were encountered: