Use Debian jessie or xenial-proposed as backports in trusty?

Colin Watson cjwatson at ubuntu.com
Tue Apr 5 11:38:03 UTC 2016


On Mon, Apr 04, 2016 at 12:21:03PM +0200, Ralf Mardorf wrote:
> On Mon, 4 Apr 2016 10:43:35 +0100, Colin Watson wrote:
> >You'll still have to deal with ensuring that your backports stay up to
> >date
> 
> If for libs the major version changed, I would move shared libs to /tmp,
> upgrade the shared libs packages and then move the old shared libs back
> and add the appropriate links.
> 
> /usr/lib/libfoo_bar.so is only used when compiling, at
> runtime /usr/lib/libfoo_bar.so.* is used, usually the major version,
> IOW /usr/lib/libfoo_bar.so.1 or /usr/lib/libfoo_bar.so.2.
> 
> /usr/lib/libfoo_bar.so -> libfoo_bar.so.2.0.0 (or 1.2.0, since it's unimportant at runtime)
> /usr/lib/libfoo_bar.so.1 -> /lib/libfoo_bar.so.1.2.0
> /usr/lib/libfoo_bar.so.1.2 -> /lib/foo_bar.so.1.2.0
> /usr/lib/libfoo_bar.so.1.2.0
> /usr/lib/libfoo_bar.so.2 -> libfoo_bar.so.2.0.0
> /usr/lib/libfoo_bar.so.2.0 -> libfoo_bar.so.2.0.0
> /usr/lib/libfoo_bar.so.2.0.0
> 
> IOW you could upgrade from 1.2.0, to 2.0.0, but keep 1.2.0.

Sure, it's perfectly sensible to keep both if you need both, but why on
earth does that require manually moving libraries around (which you
should almost never do)?  libfoo_bar.so.1* would be in a libfoo-bar1
package, while libfoo_bar.so.2* would be in a libfoo-bar2 package, and
the two should be coinstallable.  No reason to move files around by
hand.

-- 
Colin Watson                                       [cjwatson at ubuntu.com]



More information about the ubuntu-users mailing list