From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH branch/next] libgpg-error: bump version to 1.17
Date: Fri, 28 Nov 2014 15:15:17 -0300 [thread overview]
Message-ID: <5478BBB5.7090604@zacarias.com.ar> (raw)
In-Reply-To: <1417190105-22992-1-git-send-email-Vincent.Riera@imgtec.com>
On 11/28/2014 12:55 PM, Vicente Olivert Riera wrote:
> - Bump version to 1.17
> - Add a hash file
> - Add a hook to fix cross-compilation
> - Fix license and license files
> - Remove unnecessary <pkg>_CONFIG_SCRIPTS option
> - Add a positive 'depends on' for supported architectures
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
> package/libgpg-error/Config.in | 5 ++
> package/libgpg-error/libgpg-error.hash | 2 +
> package/libgpg-error/libgpg-error.mk | 73 ++++++++++++++++++++++++++++++--
> 3 files changed, 76 insertions(+), 4 deletions(-)
> create mode 100644 package/libgpg-error/libgpg-error.hash
>
> diff --git a/package/libgpg-error/Config.in b/package/libgpg-error/Config.in
> index 8287f98..2b46ffd 100644
> --- a/package/libgpg-error/Config.in
> +++ b/package/libgpg-error/Config.in
> @@ -1,5 +1,10 @@
> config BR2_PACKAGE_LIBGPG_ERROR
> bool "libgpg-error"
> + depends on BR2_arm || BR2_armeb || BR2_i386 || BR2_mips || \
> + BR2_mipsel || BR2_mips64 || BR2_mips64el || \
> + BR2_mk68 || BR2_powerpc || BR2_powerpc64 || \
> + BR2_powerpc64le || BR2_sh4 || BR2_sh4eb || BR2_sh4a || \
> + BR2_sh4aeb || BR2_sparc || BR2_x86_64
Aaand you're not propagating the new depends to all of the packages that
use libgpg-error... which may not be too wise unless the bump is really
necessary IMHO.
Also ... BR2_mk68, who's that? ;)
Regards.
next prev parent reply other threads:[~2014-11-28 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 15:55 [Buildroot] [PATCH branch/next] libgpg-error: bump version to 1.17 Vicente Olivert Riera
2014-11-28 18:15 ` Gustavo Zacarias [this message]
2014-11-28 21:39 ` Thomas Petazzoni
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=5478BBB5.7090604@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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