On Fri, 24 Apr 2015 06:41:27 +0200, Ralf Mardorf wrote:
On Thu, 23 Apr 2015 22:56:56 +0300, Jesse Jaara wrote:
What you need to do is to create a custom package for the specific version of libvpx that doesn't conflict with the one from repo, so you can have both the new version for repo packages and the old version for whatever reason
Yes, I was thinking of simply installing the new package and copying /usr/lib/libvpx.so.1.3.0 from a backup and add the links /usr/lib/libvpx.so.1 /usr/lib/libvpx.so.1.3 manually, instead of building a package for the old version.
However, I can't do this for /usr/lib/libvpx.so and the bins, that perhaps aren't needed from the old package.
It works :). I wonder if there is a good reason to move the outdated lib and links from /usr/lib/ to /usr/local/lib? I prefer to have them in the same location. $ ls -hAl /usr/lib/libvpx* lrwxrwxrwx 1 root root 15 Apr 18 12:41 /usr/lib/libvpx.so -> libvpx.so.2.0.0 lrwxrwxrwx 1 root root 20 Apr 24 07:51 /usr/lib/libvpx.so.1 -> /lib/libvpx.so.1.3.0 lrwxrwxrwx 1 root root 20 Apr 24 07:51 /usr/lib/libvpx.so.1.3 -> /lib/libvpx.so.1.3.0 -rwxr-xr-x 1 root root 1.7M Dec 7 2013 /usr/lib/libvpx.so.1.3.0 lrwxrwxrwx 1 root root 15 Apr 18 12:41 /usr/lib/libvpx.so.2 -> libvpx.so.2.0.0 lrwxrwxrwx 1 root root 15 Apr 18 12:41 /usr/lib/libvpx.so.2.0 -> libvpx.so.2.0.0 -rwxr-xr-x 1 root root 2.0M Apr 18 12:41 /usr/lib/libvpx.so.2.0.0 Regards, Ralf