From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libpcre.so.3 - Compatibility with Debian
Date: Thu, 11 Aug 2016 11:11:41 +0100 [thread overview]
Message-ID: <20160811111141.16bdfcd5@red.yakaraplc.local> (raw)
In-Reply-To: <22444.18637.297626.134016@a1i15.kph.uni-mainz.de>
On Thu, 11 Aug 2016 11:43:41 +0200
Ulrich Mueller <ulm@gentoo.org> wrote:
> >>>>> On Thu, 11 Aug 2016, James Le Cuirot wrote:
>
> > We, like almost everyone else and presumably upstream, install PCRE
> > 8 as libpcre.so.1. Debian, for reasons best known to themselves,
> > install it as libpcre.so.3. With Ubuntu still being the most widely
> > accepted "standard" Linux desktop, this presents a problem when
> > dealing with pre-compiled binaries.
>
> Have you asked Debian why they are doing that?
I did find out but had since forgotten. Here it is:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=380725#10
On that basis, this is a safe thing to do. They are indeed the same
version and there is no incompatibility.
> > [...]
>
> > I have found that creating a symlink in /usr/lib that points
> > to /lib/libpcre.so.1 works, except that when you run ldconfig, it
> > automatically creates another symlink from /usr/lib/libpcre.so.1 to
> > libpcre.so.3. If you create the first symlink in /lib instead then
> > the existing /lib/libpcre.so.1 holds after running ldconfig. The
> > latter location is therefore probably preferable.
>
> > Would anyone have any issue with adding this to our libpcre
> > package? I don't foresee any problems. libpcre.so would obviously
> > still point to libpcre.so.1. I'm pretty sure there will never be
> > another libpcre.so.3 as upstream have released PCRE2 as libpcre2,
> > effectively an entirely separate library.
>
> This looks like a bad hack. As you said above, it will confuse
> ldconfig, unless some trickery with /lib vs /usr/lib is used.
I wouldn't call it trickery. Here's what happens when you put it
in /lib. I can't see anything wrong here?
# cd /lib
# ls -l libpcre.*
lrwxrwxrwx 1 root root 16 Jul 12 23:29 libpcre.so.1 -> libpcre.so.1.2.7
-rwxr-xr-x 1 root root 464960 Jul 12 23:29 libpcre.so.1.2.7
# ln -s libpcre.so.1 libpcre.so.3
# ls -l libpcre.*
lrwxrwxrwx 1 root root 16 Jul 12 23:29 libpcre.so.1 -> libpcre.so.1.2.7
-rwxr-xr-x 1 root root 464960 Jul 12 23:29 libpcre.so.1.2.7
lrwxrwxrwx 1 root root 12 Aug 11 11:01 libpcre.so.3 -> libpcre.so.1
# ldconfig
# ls -l libpcre.*
lrwxrwxrwx 1 root root 16 Jul 12 23:29 libpcre.so.1 -> libpcre.so.1.2.7
-rwxr-xr-x 1 root root 464960 Jul 12 23:29 libpcre.so.1.2.7
lrwxrwxrwx 1 root root 12 Aug 11 11:01 libpcre.so.3 -> libpcre.so.1
> IMHO providing compatibility symlinks for proprietary binary-only
> programs isn't the task of the libpcre package.
I'm fine with putting it in libpcre-debian package as kentnl suggested.
> I remember that long time ago we had a similar issue with motif and
> icaclient (motif installing .so.4 but icaclient linking to .so.3).
> See: https://bugs.gentoo.org/show_bug.cgi?id=204264#c4
I've read through that and but I don't believe this is falling foul in
the same way. The icaclient package should not have installed a
potentially conflicting libXm symlink; libpcre-debian would be an
appropriate package. It also pointed libXm.so.3 to a different
underlying version, which may have caused breakage in other situations;
the libpcre symlink would point to the same version.
--
James Le Cuirot (chewi)
Gentoo Linux Developer
next prev parent reply other threads:[~2016-08-11 10:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 23:10 [gentoo-dev] libpcre.so.3 - Compatibility with Debian James Le Cuirot
2016-08-11 5:53 ` Kent Fredric
2016-08-11 15:41 ` Mike Gilbert
2016-08-11 18:57 ` Patrick McLean
2016-08-18 5:45 ` Daniel Campbell
2016-08-11 9:43 ` Ulrich Mueller
2016-08-11 10:11 ` James Le Cuirot [this message]
2016-08-11 10:56 ` Ulrich Mueller
2016-08-11 11:20 ` James Le Cuirot
2016-08-11 11:49 ` Kristian Fiskerstrand
2016-08-11 12:04 ` Ulrich Mueller
2016-08-11 12:13 ` Rich Freeman
2016-08-11 14:57 ` Mart Raudsepp
2016-08-11 15:03 ` Ciaran McCreesh
2016-08-11 15:05 ` Ian Stakenvicius
2016-08-11 15:15 ` Mart Raudsepp
2016-08-11 19:56 ` James Le Cuirot
2016-08-11 20:07 ` Ian Stakenvicius
2016-08-11 21:34 ` Kent Fredric
2016-08-11 22:00 ` Mike Gilbert
2016-08-12 1:19 ` Mart Raudsepp
2016-08-18 6:06 ` Daniel Campbell
2016-08-11 20:50 ` Michał Górny
2016-08-11 21:30 ` James Le Cuirot
2016-08-11 21:55 ` Mike Gilbert
2016-08-12 0:27 ` Patrick McLean
2016-08-12 0:32 ` Kent Fredric
2016-08-12 14:12 ` james
2016-08-12 15:39 ` Kent Fredric
2016-08-12 17:40 ` james
2016-08-12 17:48 ` M. J. Everitt
2016-08-12 22:36 ` Rich Freeman
2016-08-12 17:55 ` Kent Fredric
2016-08-11 16:23 ` james
2016-08-11 16:32 ` Mart Raudsepp
2026-08-13 18:27 ` james
2016-08-11 18:02 ` Matt Turner
2016-08-11 18:27 ` Deven Lahoti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160811111141.16bdfcd5@red.yakaraplc.local \
--to=chewi@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox