From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 0/2] Hack for perl module subdirectories
Date: Mon, 13 Aug 2018 23:03:45 +0200 [thread overview]
Message-ID: <20180813230345.5e2a684f@windsurf> (raw)
In-Reply-To: <20180813175645.11088-1-chrismcc@gmail.com>
Hello,
On Mon, 13 Aug 2018 10:56:43 -0700, Christopher McCrory wrote:
> for AR, CC, xFLAGS, etc. This "works", but there should be a better
> way. Hence the RFC.
>
> Also there is a package, libxml-parser-perl, that is a host only perl
> xml-parser package needed by host-intltool and metacity. Should they
> stay seprate or be merged?
libxml-parser-perl is intentionally not using the perl-package
infrastructure, because we don't want to require building host-perl to
build host-intltool.
Some libxml-parser-perl is using the system-wide Perl, which is a
mandatory Buildroot dependency.
Perhaps we should add a comment in libxml-parser-perl.mk to explain
this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-13 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 17:56 [Buildroot] [RFC PATCH 0/2] Hack for perl module subdirectories Christopher McCrory
2018-08-13 17:56 ` [Buildroot] [RFC PATCH 1/2] perl-template-toolkit: new package Christopher McCrory
2018-08-14 4:21 ` François Perrad
2018-08-15 12:03 ` Christopher McCrory
2018-08-15 18:06 ` François Perrad
2018-08-15 20:24 ` Christopher McCrory
2018-08-13 17:56 ` [Buildroot] [RFC PATCH 2/2] perl-xml-parser: " Christopher McCrory
2018-08-13 21:05 ` Thomas Petazzoni
2018-08-13 21:54 ` Christopher McCrory
2018-08-13 21:03 ` 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=20180813230345.5e2a684f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.