NEW: duckytool-0.9.6

[ecronin (Eric Cronin)]

name duckytool version 0.9.6 description ducky is ... well, the web's command line. long_description ducky marries a bunch of web service APIs into \

one tool, conventiently callable from the command \ line. search the web without using a browser.

homepage ​http://monkey.org/~jose/wiki/doku.php?id=duckytool

[pmq@…]

Committed. Thanks a lot! I have some problems with the way upstream names its executables. I committed because it seems (so far) to be a great tool, and I don't like messing/mangling with the upstream decisions (huge destroot scripts and so on). Nevertheless IMHO we should add a prefix (like 'ducky-') to these scripts (well, symbolic links). If you don't agree, I'd point out /opt/local/bin/deluser as a terrible naming mistake...

-- Pierre

[ecronin (Eric Cronin)]

I debated adding ducky- to the symlinks as well, and decided to go with the minimal set of changes for the initial portfile. Because of the way the upstream makefile is constructed, adding a prefix just requires modifying the existing reinplace command in the Portfile that adds ${destroot}${prefix}/bin to the symlinks already.

[ecronin (Eric Cronin)]

Of course, the other alternative is to not install the symlinks by default, since for example 'noaa kphl' and 'ducky.py noaa kphl' do the exact same thing. We don't do that with a lot of similar tools (openssl comes to mind immediately) already.

[pmq@…]

Hmm. I have no clear preference, even though using a prefix seems easier on the user because you can see all the available commands quickier. Listing all commands is 'ducky.py commands', so that's another step to go through if you don't remember the one you're looking for. But that's pretty minor. Anyway, I leave the last word to you =)

[pmq@…]

Committed a variant providing the links. The default is not to.