Confused by the config init --dest-dir
functionality
#2533
Labels
type: enhancement
Proposed improvement
config init --dest-dir
functionality
#2533
Describe the request
As I understand there are 3 ways to initialize the CLI config:
arduino-cli config init
will initialize the config in~/.arduino15/arduino-cli.yaml
and use~/.arduino15
as data store;arduino-cli config init --dest-file cfg.yaml
will initialize the config incfg.yaml
and use~/.arduino15
as data store;arduino-cli config init --dest-dir cfg
will create acfg
folder, initialize the config incfg/arduino-cli.yaml
and STILL use~/.arduino15
as data store.The first way is the generic default.
The second is a variant that allows you to have a different CLI config but share the package repos.
The third works exactly like the second but creates an (otherwise unused) directory. I was really surprised by this as I thought it would initialize a fully separate CLI environment. That is really useful for CI/testing purposes.
What is the use case of the
config init --dest-dir
option? Can this be edited to automatically pointdirectories.data
anddirectories.download
to the specified folder?Describe the current behavior
Currently to achieve a separate environment, the config has to be initialized and then the directories have to be manually set via
arduino-cli config set
commands.Arduino CLI version
0.35.2
Operating system
Linux
Operating system version
--
Additional context
No response
Issue checklist
The text was updated successfully, but these errors were encountered: