Nautilus scripts

Pietro Battiston toobaz at
Tue Dec 15 14:38:09 GMT 2009


being a fan of Nautilus scripts, I wrote my program gallery-uploader
([0], should be in Lucid) so that it can also be used as such (and I
personally do use it as such).

But then, I noticed that the only way to enable a nautilus script is, as
far as I know, to link it from ~/.gnome/nautilus-scripts . This kind of
defeated my purpose of creating something which could be useful even to
people not knowing how to use a terminal/fiddle with hidden files.

nautilus-script-manager ([1]) theoretically aims at solving this... but
it seems to be dead upstream, and most importantly it is still a
command-line utility.

That's why I created my nautilus-scripts-manager ([2], notice the "s" in
"scripts"), which is now in the NEW queue, waiting to enter Debian.

Now: both nautilus-script-manager and a handful of nautilus scripts also
packaged (only in Ubuntu) follow the rule that the system-wide installed
scripts lie (or are linked) in /usr/share/nautilus-scripts . So I
followed this rule too in installing gallery-uploader, and assumed it is
followed while writing nautilus-scripts-manager - in the end, I thought
it was better to follow an arbitrary one that to arbitrarily create a
new one.

However, my sponsor for nautilus-scripts-manager in Debian expressed
some doubts about the assumption, so I'm here asking: what do you
suggest I should do?

I figured out 2 possibilities:
1) keep on using /usr/share/nautilus-scripts
2) use $PREFIX/share/nautilus-scripts , and look for
$PREFIX/share/nautilus-scripts and $PREFIX/local/share/nautilus-scripts
in nautilus-scripts-manager.

Notice that for what concerns Debian/Ubuntu, there is almost no
practical difference between 1) and 2) (I'm not aware of any
non-packaged nautilus script configured to be installed system-wise)...
but still, I'd like to know which is the best solution... and it is not
necessarily one of the two.

Also notice that all this applies independently from the fact that in
next release of my utility I'd like it to support also user-provided
(not only system-wise installed) scripts.

I'd also like to introduce into Debian a couple of the scripts currently
available in Ubuntu, such as audio-convert, and that's one reason more
for me to try to see clearly what is the best approach.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio
 firmata digitalmente
Url : 

More information about the ubuntu-desktop mailing list