public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] libpcre.so.3 - Compatibility with Debian
Date: Thu, 11 Aug 2016 08:13:52 -0400	[thread overview]
Message-ID: <CAGfcS_kh42od3+-P+qgeT84DH82j4sOeWrCJDEH8CXB=L0u87w@mail.gmail.com> (raw)
In-Reply-To: <22444.27056.373109.706105@a1i15.kph.uni-mainz.de>

On Thu, Aug 11, 2016 at 8:04 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
>>>>>> On Thu, 11 Aug 2016, James Le Cuirot wrote:
>
>> That makes it slightly more awkward for binaries you may have
>> installed manually.
>
> It is impossible to support all third-party binaries, especially if
> they link against non-standard libraries because they aim for bug
> compatibility with another distro.
>
> Users manually installing such things can easily create any needed
> compatibility symlinks in their /usr/local/lib*.
>

It doesn't hurt for people to try to provide compatibility when the
changes are minor though.

It is nice to have the steam overlay around.  Though, if things got
bad enough I imagine I'd take the time to figure out how to just get
Ubuntu+Steam working in a container.  For binary packages sometimes it
is easier to just go the path of least resistance.  Though, when X11
is involved containers aren't always painless.

-- 
Rich


  reply	other threads:[~2016-08-11 12:14 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
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 [this message]
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='CAGfcS_kh42od3+-P+qgeT84DH82j4sOeWrCJDEH8CXB=L0u87w@mail.gmail.com' \
    --to=rich0@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