Ant installation targets are not package-manager safe

[Ronald Kinard]

Currently, the ant "install" and "uninstall" targets install directly to /usr folders in the File System Hierarchy. These folders are typically meant to be managed by the package manager, and not for build scripts, as to avoid conflicts with testing software and deployment software.

The Ant script should support a prefix variable that would replace /usr, and default to /usr/local, but be changeable for packaging recipes to direct to /usr; this is normal for Makefile targets.

Please see http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY

[Ronald Kinard (furyhunter)]

It just occurred to me that it isn't common for ant scripts to even have "install" and "uninstall" but rather a "dist" target that packages it up.

Package recipes should be used to do actual system installations. That's a distro-dependent thing (i.e. making an installer package for Windows, one of those app folder things in OSX), but we can make a recipe for Debian-based things directly in Launchpad. I'll consider working on that.

[tak (tak)]

Yes, I planned on having the ant script build into a .deb however the current ant instilation sceme supports every platform medusa supports including osx. Having a ppa setup, ant automated .deb building would be a nice to have. The medusa gui is already relatively popular and breaking the ant instlation features would currently not be ideal

[tak (tak)]

Thanks for the commit, the paths being updated in the ant script is definitely a better solution, and the icon not depending on the path also works better.

[tak (tak)]

I didn't realise you removed the ant install features 0.0
ant install is a standard: http://en.wikibooks.org/wiki/Apache_Ant/Best_Practices/Standard_Targets
The only thing that was not standard was ant uninstall which is supposed to be handled by the clean target however I thought clean was too arbitrary for the removal of the installed software, to keep the code standard I have now replaced uninstall with more commands added to the clean target.

I'm going to add the functionality to package it into a deb with ant eventually, however for this release the ant install features will be the primary method of setting up the software, the location it places its self in however will be changed to be standard.