public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Suggestion to drop "pcre" from default enabled USE flags in profiles
Date: Wed, 6 Jun 2012 14:53:30 -0400	[thread overview]
Message-ID: <201206061453.31258.vapier@gentoo.org> (raw)
In-Reply-To: <1339006007.2706.51.camel@belkin4>

[-- Attachment #1: Type: Text/Plain, Size: 908 bytes --]

On Wednesday 06 June 2012 14:06:47 Pacho Ramos wrote:
> The problem is that grep keeps linked against libpcre and it can cause
> problems like pointed in referred bug report, and it's really risky as
> people can have their portage completely broken for example when libpcre
> is downgraded for some reason. That doesn't sound like a good *default*
> behavior for me

there are plenty of core tools that can be broken by other packages forcing 
broken behavior like library downgrades.  and FEATURES=preserve-libs would 
gracefully handle this.

off the top of my head, lib dependencies that can bring a system down:
 - bash links against ncurses & readline
 - sed links against acl
 - coreutils links against acl/libcap/selinux/gmp
 - grep links against pcre
(with at least USE=acl being a profile default)

so highlighting the grep/pcre dep doesn't seem like it accomplishes much
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-06-06 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  8:26 [gentoo-dev] Suggestion to drop "pcre" from default enabled USE flags in profiles Pacho Ramos
2012-06-06  8:37 ` "Paweł Hajdan, Jr."
2012-06-06  8:52   ` Pacho Ramos
2012-06-06 17:23 ` Mike Frysinger
2012-06-06 18:06   ` Pacho Ramos
2012-06-06 18:53     ` Mike Frysinger [this message]
2012-06-06 19:18       ` Pacho Ramos

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=201206061453.31258.vapier@gentoo.org \
    --to=vapier@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