From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Why does glib select libpcre ?
Date: Thu, 20 Oct 2016 09:25:46 +0200 [thread overview]
Message-ID: <20161020072546.4lnhfvvq7sy4ok7b@pengutronix.de> (raw)
In-Reply-To: <CABDcavZkkQXAacgEU2PbBz3CpaKOPPAUcPxJMmZzSrBT3w23xg@mail.gmail.com>
On Fri, Oct 14, 2016 at 10:07:23AM +0200, Guillermo Rodriguez Garcia wrote:
> 2016-10-13 19:52 GMT+02:00 Robert Schwebel <r.schwebel@pengutronix.de>:
> > On Thu, Oct 13, 2016 at 04:10:12PM +0200, Guillermo Rodriguez Garcia wrote:
> >> 2016-10-13 15:34 GMT+02:00 Robert Schwebel <r.schwebel@pengutronix.de>:
> >> > On Thu, Oct 13, 2016 at 03:22:25PM +0200, Guillermo Rodriguez Garcia wrote:
> >> >> According to the glib documentation [1] (emphasis mine):
> >> >>
> >> >> GRegex uses the PCRE library for regular expression matching. The
> >> >> default is to use the internal version of PCRE that is patched to use
> >> >> GLib for memory management and Unicode handling. If you prefer to use
> >> >> the system-supplied PCRE library you can pass the --with-pcre=system
> >> >> option to, *but it is not recommended*.
> >> >>
> >> >> [1]: https://developer.gnome.org/glib/stable/glib-building.html
> >> >>
> >> >> I see that the glib package for ptxdist has a hardcoded
> >> >> --with-pcre=system option. Is there a reason for this?
> >> >
> >> > Copying libraries into one's source code and using local versions is a
> >> > bad habbit for people who do not have full control over their system :-)
> >>
> >> But that's a decision that is taken by the glib developers. I mean,
> >> wouldn't it be wise to use glib as they intend it to be used? They
> >> explicitly mention that the internal version has been patched, and
> >> that using the system-supplied PCRE is not recommended.
> >
> > So someone probably needs to have a look at what they patched.
>
> The docs say: "the internal version of PCRE that is patched to use
> GLib for memory management and Unicode handling"
And most distributions ignore the recommendation because they don't like
bundled libraries. So system-supplied PCRE is actually what most people
use, so I did the same in PTXdist.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2016-10-20 7:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 13:22 Guillermo Rodriguez Garcia
2016-10-13 13:34 ` Robert Schwebel
2016-10-13 14:10 ` Guillermo Rodriguez Garcia
2016-10-13 17:52 ` Robert Schwebel
2016-10-14 8:07 ` Guillermo Rodriguez Garcia
2016-10-20 7:25 ` Michael Olbrich [this message]
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=20161020072546.4lnhfvvq7sy4ok7b@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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