Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xutil_util-macros: move outside x11r7 scope
Date: Wed, 16 Dec 2015 23:42:23 +0100	[thread overview]
Message-ID: <20151216234223.6abe26c3@free-electrons.com> (raw)
In-Reply-To: <1449096338-8006-1-git-send-email-gustavo@zacarias.com.ar>

Gustavo,

On Wed,  2 Dec 2015 19:45:38 -0300, Gustavo Zacarias wrote:
> Move to package/util-macros and rename all symbols.
> They don't really require x11r7 infrastructure and are in fact needed by
> libepoxy which can be made x11r7-less.
> 
> Also add missing select in xfont_encoding for util-macros.
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>

Since you're renaming the Config.in option, some Config.in.legacy
handling is needed.


> diff --git a/package/util-macros/Config.in b/package/util-macros/Config.in
> new file mode 100644
> index 0000000..de0b5bb
> --- /dev/null
> +++ b/package/util-macros/Config.in
> @@ -0,0 +1,4 @@
> +config BR2_PACKAGE_UTIL_MACROS
> +	bool "util-macros"
> +	help
> +	  X.Org autotools utility macros

I am wondering if util-macros isn't too generic. Should we name it
xorg-util-macros ? xorg-autotools-macros ? But admittedly, that's not
matching the upstream name.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-16 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 22:45 [Buildroot] [PATCH] xutil_util-macros: move outside x11r7 scope Gustavo Zacarias
2015-12-16 22:42 ` Thomas Petazzoni [this message]
2015-12-16 22:46   ` Gustavo Zacarias
2015-12-17  0:01     ` Arnout Vandecappelle

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=20151216234223.6abe26c3@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