mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #174] Get this working on OSX #97
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#97
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mooredan on GitHub (Apr 25, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/174
Hi Dan Moore here. I've been away for a while and I'm happy to see that the project is still under development. This was an issue from way back and wasn't ever resolved. I don't have a Linux-based desktop/laptops any more and always had a mind to get this working under OSX.
With MacPorts and two small code changes, s3fs is working on my Yosemite system. Who/what is the gatekeeper these days? I would like to submit the changes.
@gaul commented on GitHub (Apr 26, 2015):
@mooredan Please submit pull requests for any changes. If you have expertise with Travis and Mac OS X it would be good to add that to our test matrix.
@ggtakec commented on GitHub (Apr 26, 2015):
@mooredan Please send pull request.
And if I not mistaken, you are the original owner of s3fs(on gc).
Thanks in advance for your assistance.
@mooredan commented on GitHub (Apr 26, 2015):
I am that person.
I have been playing with s3fs on my macbookpro, it appears to be working for what I want it to do: backups to S3. rsync worked fine. I'll put in a pull request shortly and contribute to the HOWTO.
make check doesn't work due to differences in OSX's netstat ~ I'll investigate that further
@gaul commented on GitHub (Apr 28, 2015):
Travis offers Mac OS X support:
http://docs.travis-ci.com/user/osx-ci-environment/
But they are currently not accepting multi-os build requests:
http://docs.travis-ci.com/user/multi-os/
This is likely due to capacity problems:
http://blog.travis-ci.com/2015-04-20-state-of-the-mac-infrastructure-on-travis-ci/
We could still test this in a one-off fashion by creating a
macosxbranch. @mooredan Could you look into this?@ggtakec commented on GitHub (Apr 28, 2015):
We can branch maxos, and I think it is probably not differ from master branch.
@mooredan could you help us?
@gaul commented on GitHub (Apr 28, 2015):
@ggtakec To be clear, I would like the source code to remain the same between
masterandmacosxbranches. The latter would just have a different Travis configuration until they can accommodate multi-os builds again. This would allow people like me to run Mac OS tests without access to Apple software.@ggtakec commented on GitHub (May 2, 2015):
@andrewgaul I created new branch macosx from master. :-)