Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: bump to version 2.58.1
Date: Mon, 3 Dec 2018 08:38:11 +0100	[thread overview]
Message-ID: <20181203083811.019c0f5e@windsurf.home> (raw)
In-Reply-To: <20181202172323.GB2649@scaer>

Hello,

On Sun, 2 Dec 2018 18:23:24 +0100, Yann E. MORIN wrote:

>  2- teach pkgconf to replace even more variables. This is not very
>     satisfying, and we won't be able to keep up in the long term. We
>     hould at least teach pkgconf to look for that list in an environment
>     variable, at least, to avoid tweaking the code over-and-over again.

Note that we have a pkg-config bump in the pending patches:
http://patchwork.ozlabs.org/patch/967653/. The bump is quite major, and
potentially affects how pkg-config behaves with variables. It might be
worth testing what happens, and in any case, if a solution is designed,
it should be based on this newer version of pkg-config.

For now, I will revert this libglib2 bump. I'll wait a bit for the dust
to settle, and then I will apply this pkg-config bump, which is another
risky change. The kind of stuff that is good to do early in the
development cycle :-)

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-12-03  7:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-14  7:58 [Buildroot] [PATCH 1/1] libglib2: bump to version 2.58.1 Fabrice Fontaine
2018-12-02 13:00 ` Thomas Petazzoni
2018-12-02 17:23   ` Yann E. MORIN
2018-12-03  7:23     ` Fabrice Fontaine
2018-12-03  8:11       ` Yann E. MORIN
2018-12-03  7:38     ` Thomas Petazzoni [this message]
2018-12-03  8:06       ` Yann E. MORIN

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=20181203083811.019c0f5e@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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