public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libpcre.so.3 - Compatibility with Debian
Date: Thu, 11 Aug 2016 18:15:50 +0300	[thread overview]
Message-ID: <1470928550.5563.25.camel@gentoo.org> (raw)
In-Reply-To: <4b09dfc4-b6ca-fb1b-adc3-e9c9da766a10@gentoo.org>

Ühel kenal päeval, N, 11.08.2016 kell 11:05, kirjutas Ian Stakenvicius:
> Wouldn't the most simple solution here would be to make a symlink for
> libpcre.so.3 within the local bindir for each Valve or whatever
> package that needs it?  This is a binary-package-supporting hack,
> might as well do it in the binary packages that need it.  You might
> still need to wrap the binary to set some environment stuff, not
> sure;
> either way it doesn't seem to make sense to make this a system-wide
> thing.
> 

It makes sense, IF it doesn't hurt absolutely anything as a by-product.
Also open source stuff should be gradually moving over to pcre2,
eventually ending up with libpcre.so being for binary packages
exclusively in due time anyways.


Ühel kenal päeval, N, 11.08.2016 kell 16:03, kirjutas Ciaran McCreesh:
> On Thu, 11 Aug 2016 17:57:59 +0300
> Steam isn't a use case, it's a program.

Use case is proprietary gaming and software, if that makes you happier
and avoids further useless e-mails due to feeling like nitpicking on a
perhaps very slightly wrong terminology.
Having specifically Steam hassle-free is also important on the desktop,
unless your only goal is to be a FSF endorsed distribution. But it
covers all proprietary software that targets and tests stuff working on
Debian/Ubuntu (which is the majority of cases, sadly).


Mart


  reply	other threads:[~2016-08-11 15:16 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
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 [this message]
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=1470928550.5563.25.camel@gentoo.org \
    --to=leio@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