From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/python-augeas: new package
Date: Fri, 25 Jun 2021 08:51:21 +0200 [thread overview]
Message-ID: <20210625085121.3c682b60@windsurf> (raw)
In-Reply-To: <20210624215353.GI2852@scaer>
On Thu, 24 Jun 2021 23:53:53 +0200
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > +PYTHON_AUGEAS_VERSION = 1.1.0
> > +PYTHON_AUGEAS_SITE = $(call github,hercules-team,python-augeas,v$(PYTHON_AUGEAS_VERSION))
> > +PYTHON_AUGEAS_SETUP_TYPE = setuptools
> > +PYTHON_AUGEAS_LICENSE = LGPL-2.1+
> > +PYTHON_AUGEAS_LICENSE_FILES = COPYING
> > +PYTHON_AUGEAS_DEPENDENCIES = augeas host-python-cffi host-pkgconf
> > +# This will tell python-augeas to not call xml2-config, and instead
> > +# use pkg-config to find libxml2. libxml2 is an indirect dependency of
> > +# augeas, which is why it's not in our dependencies. It's odd that
> > +# python-augeas searches for libxml2, but that's what it
> > +# does. Question asked in the pull request at
> > +# https://github.com/hercules-team/python-augeas/pull/49.
>
> They've now replied, and I am not sure I followed... Augeas' .pc does
> not yield libxml2' CFLAGS, because it is a Requires.Private.
>
> So, why does python-augeas need the CFLAGS from libxml2?
Yeah, I was also confused by their reply, and didn't investigate
further at this point.
Thanks for looking at the patch and merging!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2021-06-25 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 20:34 [Buildroot] [PATCH 1/2] package/python-augeas: new package Thomas Petazzoni
2021-06-21 20:34 ` [Buildroot] [PATCH 2/2] support/testing/tests/package/test_python_augeas: new test Thomas Petazzoni
2021-06-24 21:53 ` [Buildroot] [PATCH 1/2] package/python-augeas: new package Yann E. MORIN
2021-06-25 6:51 ` Thomas Petazzoni [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=20210625085121.3c682b60@windsurf \
--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