From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libglib2: improve dev file handling
Date: Sun, 20 Mar 2016 22:14:49 +0100 [thread overview]
Message-ID: <20160320221449.7eff12f2@free-electrons.com> (raw)
In-Reply-To: <1457621557-23336-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Thu, 10 Mar 2016 11:52:36 -0300, Gustavo Zacarias wrote:
> Remove source schema files from target
> (/usr/share/glib-2.0/schemas/*.dtd and *.xml) at target finalization
> time.
> This is because other packages install schemas as well to avoid
> duplicating file removal efforts all around.
>
> Add a schema compiler run on target finalization as well - we previously
> didn't do this since not many packages use it, however the upcoming
> connman-gtk package does require a valid gschemas.compiled to work
> properly.
> We also do this at target finalization to avoid each package handling
> this on their own.
>
> Purge some extra binaries and files from the target, like the schema
> compiler to save additional space since they're unused at run time.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> package/libglib2/libglib2.mk | 37 +++++++++++++++++++++++++++++--------
> 1 file changed, 29 insertions(+), 8 deletions(-)
Both patches applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-03-20 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 14:52 [Buildroot] [PATCH 1/2] libglib2: improve dev file handling Gustavo Zacarias
2016-03-10 14:52 ` [Buildroot] [PATCH 2/2] connman-gtk: new package Gustavo Zacarias
2016-03-20 21:14 ` 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=20160320221449.7eff12f2@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