add micromamba self-update functionality

[wolfv]

trafficstars

• [x] rerun shell init?!
• [ ] Add update notification if newer version is available?
• [x] Test (especially on Windows)
• [x] Add Windows tricks to Bash ?!

[baszalmstra]

How would you now call this? Like this?

micromamba update --self 

I think this is a bit confusing because it mixes two commands, one to update and environment and one to update the install itself. The help page of update would include arguments for both which might be confusing. I would opt to add a new sub-command for this use-case. Something along the lines of:

micromamba self-update

WDYT?

[wolfv]

yeah, it was just a placeholder to use update --self. I think self-update could be fine.

Homebrew is using update to update homebrew, and upgrade to update packages. We're already using update to update packages so we need to come up with something else I think. Also it's confusing to make upgrade and update differnt...

[baszalmstra]

Homebrew is using update to update homebrew, and upgrade to update packages. We're already using update to update packages so we need to come up with something else I think. Also it's confusing to make upgrade and update different...

Thats indeed very confusing 😅

[wolfv]

The other option would be to specialcase micromamba update micromamba and also add a stage to micromamba update --all (if executed in the root prefix). But maybe it's better to let the micromamba self-modifications live outside the normal package management...

[jonashaag]

But maybe it's better to let the micromamba self-modifications live outside the normal package management

Strongly agree!

[jonashaag]

Going to try this in a funny customer environment :)

[jonashaag]

Tested on Windows with micromamba.exe in Downloads:

error    libmamba Could not lock non-existing path 'C:\Users\USERNAME\conda-meta'
critical libmamba LockFile error. Aborting.

[wolfv]

ugh :) I get further on Windows, but then it silently crashes...

These are the last two log lines:

info     libmamba Transfer finalized, status: 304 [https://conda.anaconda.org/robostack-humble/win-64/repodata.json] 0 bytes
robostack-humble/win-64                                       No change
info     libmamba Reading cache files 'C:\Users\robostack\micromamba\pkgs\cache\5afe41e9.*' for repo index 'https://conda.anaconda.org/conda-forge/win-64'

[AntoinePrv]

Should the documentation be updated to inform users of that feature?

[wolfv]

Yes, for sure!