Add execute permissions to bun executables in bun-versions

[daradermody]

The bun executables are added to ~/.bum/bun-versions with read and write permissions, but not executable.

Is it possible to change this to be executable for the user and the group (e.g. 774 instead of 664) so it looks like this?

My use case is to run my application using a systemd service in the background, but using a specific version of Bun so I can change Bun versions for my other projects while that service still uses the specific version. Otherwise it might break if I bum use a newer version of Bun with some breaking changes.

I can get around this by manually running chmod +x, but I thought it might be worth bum doing it automatically, which is what nvm does:

On a more generaly note, it looks like when I bum use, it affects all sessions. For example, if there is a person SSHed on to a server using a version of Bun (e.g. 1.2.4), then another person SSHes onto the same server with the same user and runs bum use 1.2.8, the first person's Bun will be affected and use 1.2.8 without them noticing. It'd be nice if there was independance like with nvm; in the above scenario, the two people can use two different node versions at the same time (because it uses aliases or something rather than copying/hardlinking ~/.bun/bin/bun).

[owenizedd]

I have been wanting to do the permission actually.

For the aliases I haven’t actually tried to see how it is being implemented.

Will do latter when I have the motivation :)
For permission will see, i will try to work on it