From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Why does glib select libpcre ?
Date: Thu, 13 Oct 2016 16:10:12 +0200 [thread overview]
Message-ID: <CABDcavZ0h7RzBGsO_cAtxCT_kAMMsV+pqTSJ072rWoE7WtSn2w@mail.gmail.com> (raw)
In-Reply-To: <20161013133446.ptmosbmebaqm35sr@pengutronix.de>
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.
--
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-13 14:10 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 [this message]
2016-10-13 17:52 ` Robert Schwebel
2016-10-14 8:07 ` Guillermo Rodriguez Garcia
2016-10-20 7:25 ` Michael Olbrich
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=CABDcavZ0h7RzBGsO_cAtxCT_kAMMsV+pqTSJ072rWoE7WtSn2w@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--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