-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Req] Combine home share and root share? #61
Comments
Adding environ expansion it to existing options might break someone's setup if they already shared a folder with Also just using |
Extending root share would effectively satisfy this request. This would also allow read-only shares in the home folder with portable instance folders.
Would also be useful to extend with following features:
I believe some of the above are already provided by I'm picturing a GUI that looks like a table, with entry fields and checkboxes:
If you allow full variable expansion, wouldn't os.path.expandvars take care of I'm fine with dropping |
Kind of reminds me of a volume system that docker/podman used. It has been already been discussed in #56 . As for expanding variables for paths. Only as a new option. Backwards compatibility is very important. |
That would be fine with me.
What about a new share system that stores paths in the toml as lists? As long as new options are added only to the end of the list, backwards compatibility can be maintained with future expansions. (Extra or missing options can be ignored.)
|
Description
Since both home share and root share both use the same
bwrap --bind
option, why not unify them and allow~
,$HOME
, and other select variables ($XDG_*
)?The text was updated successfully, but these errors were encountered: