From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/8] python-libxml2: new host package
Date: Sat, 5 Nov 2016 11:29:28 +0100 [thread overview]
Message-ID: <20161105112928.73a588b0@free-electrons.com> (raw)
In-Reply-To: <cc97f194-ec81-9b44-fe2f-a1467873a279@mind.be>
Hello,
On Sat, 5 Nov 2016 00:47:04 +0100, Arnout Vandecappelle wrote:
> >> * The libxml2 package gains a sub-option
> >> BR2_PACKAGE_HOST_LIBXML2_PYTHON, which allows to enable python
> >> support. Of course, later we could add BR2_PACKAGE_HOST_LIBXML2 as
> >> well, and fix the packages that depend on host-libxml2, but it can
> >> be done later.
> >
> > We currently have no BR2_PACKAGE_HOST_LIBXML2 option so we should add that and
> > make host-libxml2 depend on host-python when the python option is enabled, and
> > make packages select host-libxml2 as well (+ python for host-itstool).
> > It's basically a half-way to achieving the first point, even though quick i'm
> > not a big fan.
>
> I'm also no big fan. Especially because the first one is where we want to go
> eventually, so this would really just be a stop-gap measure.
Well, between option (1) and (2) that I proposed, it's the same debate
between "implicit dependencies" and "explicit dependencies", which we
already have for target packages:
- Option 1 is: the host-libxml2 package automatically enables its
Python binding if host-python is enabled.
- Option 2 is: the host-libxml2 has a sub-option that allows to
explicitly enable/disable its Python binding
Just like we have a mix of (1) and (2) for target packages depending on
the situation, I guess we might have a similar mix for host packages,
no?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-11-05 10:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 1:13 [Buildroot] [PATCH 1/8] gsettings-desktop-schemas: bump to version 3.22.0 Gustavo Zacarias
2016-10-13 1:13 ` [Buildroot] [PATCH 2/8] adwaita-icon-theme: install to staging Gustavo Zacarias
2016-10-16 16:15 ` Thomas Petazzoni
2016-10-17 10:08 ` Gustavo Zacarias
2016-10-17 20:30 ` Arnout Vandecappelle
2016-10-13 1:13 ` [Buildroot] [PATCH 3/8] poppler: add explicit cairo support Gustavo Zacarias
2016-10-15 9:33 ` Peter Korsgaard
2016-10-13 1:13 ` [Buildroot] [PATCH 4/8] poppler: add explicit libglib2 support Gustavo Zacarias
2016-10-15 9:34 ` Peter Korsgaard
2016-10-13 1:13 ` [Buildroot] [PATCH 5/8] poppler: bump to version 0.48.0 Gustavo Zacarias
2016-10-15 9:35 ` Peter Korsgaard
2016-10-13 1:13 ` [Buildroot] [PATCH 6/8] python-libxml2: new host package Gustavo Zacarias
2016-10-28 13:32 ` Thomas Petazzoni
2016-10-28 13:42 ` Gustavo Zacarias
2016-11-04 23:47 ` Arnout Vandecappelle
2016-11-05 10:29 ` Thomas Petazzoni [this message]
2016-10-13 1:13 ` [Buildroot] [PATCH 7/8] itstool: " Gustavo Zacarias
2016-10-13 1:13 ` [Buildroot] [PATCH 8/8] evince: new package Gustavo Zacarias
2016-10-15 9:32 ` [Buildroot] [PATCH 1/8] gsettings-desktop-schemas: bump to version 3.22.0 Peter Korsgaard
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=20161105112928.73a588b0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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