2016-06-07 23:43 GMT+02:00 jd1008 <[email protected]>: > It really needs an installer that will put all those files into the > appropriate > >> directories, same as how installing an rpm does. > >> As it is, I cannot (will not) use it because I will have to put it into a > separate directory > to which my PATH env will point, and I dont want to keep mucking with that.
Feel free to make one ;) RPM packages do exist, but I'm not sure how well this will work with FC20: http://rpmfusion.org/ The remark about the need to update is that security fixes are most likely not backported that far. That pose a security threat as many vulnerabilities will apply to the system. Of course if it stay off the internet and *always* get its input from safe source, whatever. F20 end of life was (according to wikipedia) at the end of 2013. Alternatively, it is not uncommon to have a ~/bin directory in your path, and quite tidy too. Also, ffmpeg static builds don't need any extra file to operate beside the binary; you only need the ffmpeg binary somewhere. You can even drop it in your system binaries directory (something like /usr/local/bin is made for that, at least in Debian-based systems). _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
