search

openpreserve / scape-toolwrapper

SCAPE project for creating debian packages from command line tools.
http://openplanets.github.io/scape-toolwrapper
Apache License 2.0
5 stars 1 forks source link

If installed file has the same name as the operation it is not installed. #12

Closed luis100 closed 10 years ago

luis100 commented 10 years ago

If a binary is included, there may be a tendency for the name of the wrapper to be the same and so it would be overwritten on install. A simple solution would be to detect this case and rename the tool wrapper bash script to have a "-wrapper" suffix.

hsilva-keep commented 10 years ago

Closing this ticket as I consider it a non-issue. The created wrapper location is beneath /usr/bin and all the "installable" files are located under /usr/share/OPERATION_NAME/.

alastairduncan commented 10 years ago

What happens if you have a binary file? How should this be distributed?

hsilva-keep commented 10 years ago

As I stated in the previous comment, the binary (and other installable files that are put in the special folder install) will be located under /usr/share/OPERATION_NAME... You may say that if the binary is architecture dependent it isn't the right place for it. Well, the toolwrapper acts this way, i.e. to put them all under /usr/share/OPERATION_NAME, to simplify life of the ones that use it so everyone knows were the files they wanted to install are located. This feature was added to ease the process of describing operations (toolspec and component spec) and at the same time package the developed tools. If the toolwrapper doesn't fulfil your needs unfortunately you will have to do yourself the packaging to put stuff in their right places.