-
Notifications
You must be signed in to change notification settings - Fork 76
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
Can we add fuse-t option? #137
Comments
By the way, can we use GitHub Actions to compile the source code into binary artifacts and store them using releases. Similar to the example provided at https://github.com/cnpm/unionfs-fuse/actions/runs/5584483192, we can set up a workflow that automatically compiles the code and generates the desired binary files. These files can then be uploaded and attached to releases for easy distribution and access. |
wow! thanks! if you create a pr i'll gladly merge it. please be sure not to remove the "old" osxfuse build option. also, if there's a way to run tests locally (as opposed to github actions) via vagrant or something that would add extra piece of mind since i have no mac computer to test it. but i'd merge it even without tests... |
Just wanted to thank's @killagu for the work, cloned you repo and followed the github actions to build myself. Thank you so much both of you for this great piece of software! |
What is fuse-t?
https://www.fuse-t.org/
Fuse-t is a completely user-space implementation based on the NFS protocol. It does not require disabling various security measures on macOS during installation and does not cause any system instability.
How to implement?
I have already forked it at https://github.com/cnpm/unionfs-fuse, made modifications to the compilation configuration, and successfully run it.
As for the implementation method, we can add a compilation option called WITH_FUSE_T.
If it's possible, I can submit a PR to support this feature.
The text was updated successfully, but these errors were encountered: