Useful e.g., when passing multiple icons with different resolutions via -i, if they have the resolution in the filename.
Also removes all traces of that appName concept that has been abandoned.
The input plugins can use this environment variable to call linuxdeploy themselves. This can be very handy to have it deploy additional dependencies on libraries they copy themselves.
An alternative approach is to simply use liblinuxdeploy inside the plugin, like the Qt plugin does.
Also uses the native split functionality provided by the utils module
instead of some external dependency's.
Preparation for using this method in plugins such as the Qt plugin.
deployFile allows for specifying a directory as destination, and copies
files into there, simulating the behavior of tools like cp. To do that,
it creates the directory, then appends the filename of the input file
to it and uses that as destination for the "copy file" call.
It's pretty handy for some applications to get the full path of the
new file returned by this method directly (doesn't have to implement
this concatenation more than once).
GoogleTest internally uses operator==(first, second) instead of
first.operator==(second). By implementing the operators outside the
classes, GoogleTest can be made happy.
* Add symlinkFile to the public AppDir interface
* Rename AppDir::symlinkFile to AppDir::createSymlink
* change return value to bool
* Remove duplicated header
* Remove blank lines
* Add comment
* Fix test name
* Change createSymlink signature. Name changed to createRelativeSymlink and remove the useRelativePath argument
* Remove commented tests.
TheAssassin
Alexis López Zubieta