#Best practices around using version manager tools?

14 messages · Page 1 of 1 (latest)

uncut cave
#

For context, I'm referring to tools similar to mise (https://mise.jdx.dev/), which i will use as the example here.

I followed the installation instructions for mise (i.e. curl https://mise.run | sh), which installs to ~/.local/... by default.

Some questions I have:

  1. how does the isolation work for vso shell and subsystems in general? I think I ran the installation in vso shell and found myself surprised that mise (and anything I installed with it) became available system-wide (i.e. can be invoked by other subsystems). I even wiped the mise installation and reran the installation command in a new subsystem that I created, but the result seemed to be the same. I thought that it would be only available in that subsystem and I would have to export the bins. Is ~/.local/... some special case?

  2. follow-up to 1: is it okay that such a tool is installed as a system-wide thing? My initial intuition was that it would be more "idiomatic" to have it isolated within its own subsystem, exporting things as necessary. part of me thinks that this would be inconvenient though

  3. are changes to files like ~/.bashrc not isolated per subsystem? seems like that's the case but for some reason I thought each subsystem would have their own version of the file.

Maybe i don't really understand subsystems well enough yet. Part of me feels like I'm "holding it wrong" in this case, even though it currently works for me. Haven't read through the docs in full yet (I find them generally hard to navigate).

Home | mise-en-place

mise-en-place documentation

#

Best practices around using version manager tools?

fair goblet
#

Basically the answer for all your questions is the same: apx subsystems share the same home folder

#

Your home folder and mounted USB drives and more are mounted volumes from the host

#

That also allows you to have access to all your files like normal without using weird paths

#

You can create a subsystem with it's own home folder if needed via command line if you want more isolation

uncut cave
#

ah that clarifies a lot! i don't remember coming across that detail in the docs i read but i could've easily skimmed over it given my head was trying to process a variety of other things 😅

#

i guess I'm wondering if there's any major downside to having a tool like mise (and anything managed by it) shared between all subsystems. seems like it's serving me well but curious how others generally approach it

#

btw thanks for the quick response!

fair goblet
#

If you install it what would usually be "systemwide" on a normal distro, then it would be only for that specific subsystem

uncut cave
#

ah sorry i'm probably using "systemwide" incorrectly in my original post.

fair goblet
#

I don't think it will be a problem, might not work in all subsystems if it needs specific other packages to run

fair goblet
uncut cave
#

right makes sense