Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] automake: bump version to 1.15
Date: Tue, 06 Jan 2015 08:35:28 -0300	[thread overview]
Message-ID: <54ABC880.3090400@zacarias.com.ar> (raw)
In-Reply-To: <54ABC4F5.9060605@imgtec.com>

On 01/06/2015 08:20 AM, Vicente Olivert Riera wrote:

> No, I have only tried to compile those packages depending on
> "host-automake": freetype, sdl, gpm and znc, if I recall correctly. Is
> not enough? I can do an allyespackageconfig if you require it.

AUTORECONF pulls host-automake in as well, so it's not just the
face-value ones.
I do not require anything (for this, i still eat hehe) :)
It's just a "how much breakage" we can expect from this question if you
did the test so it would be convenient since some fixes will possibly be
required.
Normally some of those "warning blah this blah other" you see when
autoreconfing a package can become an error with major bumps since they
sit in deprecated mode (warning) for a couple of releases until it goes
into removal.
The usual problem is with old packages that haven't seen a release in
some time and hence didn't update their auto* stuff accordingly, or devs
who haven't kept up with new auto* stuff/releases.
Regards.

  reply	other threads:[~2015-01-06 11:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-06  9:07 [Buildroot] [PATCH] automake: bump version to 1.15 Vicente Olivert Riera
2015-01-06 11:08 ` Gustavo Zacarias
2015-01-06 11:20   ` Vicente Olivert Riera
2015-01-06 11:35     ` Gustavo Zacarias [this message]
2015-01-06 11:55       ` Vicente Olivert Riera
2015-01-06 13:45   ` Thomas Petazzoni
2015-01-06 13:48     ` Gustavo Zacarias
2015-01-06 13:55       ` Vicente Olivert Riera
2015-01-06 14:57         ` Vicente Olivert Riera
2015-01-06 15:19           ` Gustavo Zacarias
2015-01-06 15:22             ` Vicente Olivert Riera
2015-01-07 21:11 ` 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=54ABC880.3090400@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