Developer discussion for Creative Commons technology and tools

[Sebastian Pipping <webmaster AT hartwork.org>]

Asheesh Laroia wrote:
>> 4) See what related files nautilus is accessing on startup:
>>  $ strace nautilus 2>&1 | grep /usr/lib/.\*nautilus
>>  open("/usr/lib/libnautilus-extension.so.1", O_RDONLY) = 3
>>
>> What's next?
> 
> Try putting the CC Nautilus extension in the path that Nautilus looks in
> for Python extensions and see if you get a new properties pane.
> 
> But one more thing:
> 
>>  /usr/lib/pkgconfig/nautilus-python.pc
>>  /usr/share/doc/nautilus-python/README
>>  /usr/share/doc/nautilus-python/documentation.py
>>  /usr/share/doc/nautilus-python/examples
>>  /usr/share/doc/nautilus-python/examples/background-image.py
>>  /usr/share/doc/nautilus-python/examples/block-size-column.py
>>  /usr/share/doc/nautilus-python/examples/md5sum-property-page.py
>>  /usr/share/doc/nautilus-python/examples/open-terminal.py
> 
> Can you get these files to work? What does README or documentation.py say?

README says I should copy the examples to one of

  /usr/lib/nautilus/extensions-1.0/python/
  ~/.nautilus/python-extensions/

However Nautilus does not seem to look into that, both

  strace nautilus 2>&1 | fgrep extensions
  strace nautilus 2>&1 | fgrep .nautilus/python-extensions

give nothing.

I cannot make any sense from documentation.py with my
current knowledge of Python.

The 0.4.1-r1 ebuild I've been using latest can be found
at [1] if anybody feels like playing around with it.



Sebastian


[1]
http://git.goodpoint.de/?p=overlay-sping.git;a=tree;f=gnome-extra/nautilus-python;hb=HEAD