search

Crystal03 / google-docs-fs

Automatically exported from code.google.com/p/google-docs-fs
GNU General Public License v2.0
0 stars 0 forks source link

Mac OS X install instructions unclear #42

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Attempt to follow the instructions for Mac

What is the expected output? What do you see instead?
Successful installation.
Instead, one is confused: where to fetch pkg-config? Which version of 
fuse-python to get? Where to get fuse-python? How to build these?

What version of the product are you using? On what operating system?
Tip changeset: 
  82:aac84cf53843

Please provide any additional information below.
I have tried to follow the instructions once again, this time trying to use 
only built-in Mac Python.  Here's what I did.

Step 1:
Confirm having MacFUSE installed. 
Confirmed: NTFS-3G works.

Step 2:
Install pkg-config. 
Opted for a pre-compiled binary, built as part of Rudix: 
http://rudix.org/packages-opq.html

Step 3:
Install fuse-python.
Opted for cloning hg repository from 
http://mercurial.creo.hu/repos/fuse-python-hg 

Here's where I'm stuck. While this would commonly mean I should report a bug to 
FUSE-Python, it is sad that google-docs-fs contains instructions on installing 
on Mac OS X, but does not contain a very good description of which version of 
software, and whose release of software, its instructions presume the user to 
have.

Instructions could be improved by mentioning if user should fetch pkg-config 
and fuse-python from MacPorts, from Rudix, from Fink, or from source. If 
possible, they could mention the exact commands to be cut-and-pasted into the 
command line.

As is, the number of google-docs-fs users on Mac is bound to stay low; I'm 
neither a newbie with development, nor with Python, and by the existence of 
MacPorts on my machine, obviously not a "dumb casual end-user" either. Yet, I 
couldn't get google-docs-fs to work in a reasonable amount of time.

It is more than understandable if the developer does not have a Mac; it is more 
than understandable either way since this is a free project. But, whoever wrote 
the instructions could do just a tiny little bit more, and give the project 
tons of happy users. As is, Mac instructions are not very useful, since they 
presume extreme will and knowledge from the users. This can't be presumed nor 
expected on any platform, not even Linux.

Original issue reported on code.google.com by ivuc...@gmail.com on 15 Nov 2010 at 5:46

GoogleCodeExporter commented 9 years ago 
To be less useless, I've written a few tips here: 

http://blog.vucica.net/2010/11/some-tips-on-building-fuse-python-on-mac-os-x.htm
l

I've also made a public clone on Google Docs; there are some fixes I'm trying 
out for OS X, and if I manage to do anything, I'll push the changes there.

Original comment by ivuc...@gmail.com on 15 Nov 2010 at 6:59

GoogleCodeExporter commented 9 years ago 
Thanks, it's much appreciated. I'll post a link to this on the main Wiki too so 
more people can see it.

Original comment by d38dm8nw81k1ng@gmail.com on 26 Dec 2010 at 1:40

GoogleCodeExporter commented 9 years ago 
By far the easiest way to install the python fuse bindings is this: 

sudo port install fuse-bindings-python25
cp -r /opt/local/lib/python2.5/site-packages/fuse* 
/Library/Python/2.6/site-packages/

Original comment by firm...@gmail.com on 9 Jan 2011 at 4:57

GoogleCodeExporter commented 9 years ago 
In addition to the #1's guide, I had to also follow this guide to get over the 
"lipo: can't open input file" error: 
http://passingcuriosity.com/2009/installing-pil-on-mac-os-x-leopard/

Original comment by harid...@gmail.com on 3 Aug 2011 at 6:27