If packaged as a deb, woof downloads the file with -U in its folder, right? But packaging it as a .deb, the woof folder would be /usr/bin so it would attempt to download the files received with -U in the /usr/bin folder which is of course impossible. Unless woof is ran with "sudo" which is the worst thing anyone can do :)
That's why a configuration for where the files are saved is a must.
Also, once the other security issues are fixed, sure... I can package woof. It doesn't need compiling or anything so it's quite easy to do (as long as there's a readme with all the woof dependencies - which by the way is currently missing).
Hello,
If packaged as a deb, woof downloads the file with -U in its folder, right? But packaging it as a .deb, the woof folder would be /usr/bin so it would attempt to download the files received with -U in the /usr/bin folder which is of course impossible. Unless woof is ran with "sudo" which is the worst thing anyone can do :)
That's why a configuration for where the files are saved is a must.
Also, once the other security issues are fixed, sure... I can package woof. It doesn't need compiling or anything so it's quite easy to do (as long as there's a readme with all the woof dependencies - which by the way is currently missing).