Matthew Kenigsberg
Matthew Kenigsberg
Merged to activate-feature-branch but not main yet so I'm leaving this open for now
I don't think we want to add a blocking network call by default as part of activating a pulled environment because it could significantly slow down activate, which we want...
@dcarley put this list of variables together https://docs.google.com/spreadsheets/d/1C70LAk2iUeMFL4V3HITMMueIVXfr7CQL5hrpu_3I_QM/edit?gid=0#gid=0
One option for this would be supporting Renovate. Request for that in https://github.com/flox/flox/issues/3409
> Also, does the flox CLI have a command to only refresh the lock file? Running flox upgrade does not do that. I found out that EDITOR=cat flox edit refreshes...
It sounds like you're thinking you'd have: ``` [install] python3.pkg-path = "python3" python3.version = "3.13.4" ``` And then when `3.13.5` was released, renovate would change `3.13.4` -> `3.13.5` Would it...
All packages in the same package group have to be upgraded in the same time, but if a package is in its own package group you can e.g. `flox upgrade...
> considering that the semantics are different ones ("container target" vs "building runtime") i'd prefer a separate flag In some sense the semantics are different, but we're asking the user...
> Is the primary need for this if you have both installed and want to override the auto-detection order? Yep
> 1. No args > a. Detect proxy runtime, and > b. Detect output runtime or write to default file > > 2. `--runtime foo` > a. Use `foo` for...