public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Campbell <zlg@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] libpcre.so.3 - Compatibility with Debian
Date: Wed, 17 Aug 2016 23:06:02 -0700	[thread overview]
Message-ID: <ae5b067e-7465-380e-b348-fa549cc65c87@gentoo.org> (raw)
In-Reply-To: <1470964747.5563.43.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 3352 bytes --]

On 08/11/2016 06:19 PM, Mart Raudsepp wrote:
> Ühel kenal päeval, N, 11.08.2016 kell 18:00, kirjutas Mike Gilbert:
>> On Thu, Aug 11, 2016 at 5:34 PM, Kent Fredric <kentnl@gentoo.org>
>> wrote:
>>> On Thu, 11 Aug 2016 16:07:27 -0400
>>> Ian Stakenvicius <axs@gentoo.org> wrote:
>>>
>>>> but realistically this should be
>>>> installed to /usr/$(get_libdir)/debiancompat/ or similar, and if
>>>> you
>>>> still don't want to wrap the apps that need it then also install
>>>> an
>>>> /etc/env.d/ file to add this dir to the LDPATH.
>>>
>>> +1 to this. I was going to suggest something similar.
>>>
>>> At least, because I'm still thinking in a view other than "steam",
>>> and
>>> anticipating "Maybe we're going to do more of this"
>>>
>>> If more than one binary application need more than one debian hack,
>>> stuffing all the debian hacks in a special prefix that everyone can
>>> use
>>> without polluting the main gentoo stuff is an advantage.
>>>
>>> ( And the separate dir makes it clear what the library is for and
>>> why
>>> its there if anyone is trying to weed out some library problem that
>>> still manages to happen despite our attempts )
>>
>> I also like the private libdir better than installing a symlink in a
>> "standard" libdir.
> 
> The question is really why, still.
> I only see some sort of tidyness arguments, but it's not exactly tidy
> to clobber ld.so.conf either, so I don't consider this a real argument.
> 
> If you install a proprietary package from their .tar.bz2 or Loki .sh
> installer or whatever, the user will not know to install some libpcre-
> debian package.
> Also, again, PCRE2 is there. Soon dev-libs/libpcre:3 (libpcre-8.*) is
> primarily a binary package satisfier anyways, so why not just satisfy
> libpcre.so.3 while at it. Funny fact - we have it in SLOT=3 too :)
> 
> Ultimately I don't care personally as a gentoo user, as I will know to
> install this useless symlink package. Maybe, if I remember. And only
> because of a 10+ thread. But our users are uselessly bothered when they
> actually need it by something.
> They ought to be able to choose to not care, and have shit working out
> of the box. This is providing a very important choice, in the spirit of
> Gentoo.
> 
> 
> Mart
> 
We normally have our differences but I have to agree here. Getting
proprietary stuff to work at all is a pain; being able to simply not
care and "just make it work" would be great. I think we can do it no
matter where we choose to install things. iirc the steam-meta package
already includes a wrapper.

Given that Valve only promises support on Ubuntu (and SteamOS which is
basically Ubuntu), we should probably use a Debian/Ubuntu-specific
compat dir so we can address all future kludges instead of just PCRE.

But really, we should be able to make it so users can `emerge -a steam`,
wait a few minutes, and be able to type "steam" into a terminal or run
dialog and it "just works". Skype does it; I don't see why Steam can't,
unless there's a licensing problem.

(This is my perspective as a user who begrudgingly uses Skype and Steam,
and has historically had more trouble from Steam)
-- 
Daniel Campbell - Gentoo Developer
OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net
fpr: AE03 9064 AE00 053C 270C  1DE4 6F7A 9091 1EA0 55D6


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-08-18  6:06 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
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 [this message]
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=ae5b067e-7465-380e-b348-fa549cc65c87@gentoo.org \
    --to=zlg@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