From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libtool version update 2.4.2
Date: Sun, 11 Nov 2012 23:05:46 +0100 [thread overview]
Message-ID: <20121111230546.709735e3@skate> (raw)
In-Reply-To: <50A02018.1000804@mind.be>
On Sun, 11 Nov 2012 23:00:56 +0100, Arnout Vandecappelle wrote:
> On 11/10/12 10:53, Thomas Petazzoni wrote:
> > Alexander,
> >
> > On Fri, 9 Nov 2012 16:38:52 +0400, Alexander Khryukin wrote:
> >
> >> -LIBTOOL_VERSION = 2.2.10
> >> +LIBTOOL_VERSION = 2.4.2
> >
> > How much testing did you give to this version bump? A libtool
> > version bump is a very sensitive operation, as host-libtool is used
> > to autoreconfigure many packages in Buildroot. Therefore, this
> > patch needs a good amount of testing before being committed
> > (ideally testing that all packages having<foo>_AUTORECONF = YES
> > still build).
>
> Can't we rely on the autobuilders to do that?
Sure, we'll certainly rely on the autobuilders for a complete testing.
But I wanted to know if it had been tested again 2 packages or 20-40
packages, which makes quite a bit of difference :)
> That said, I wouldn't do this for 2012.11 anymore...
For sure, it should not be part of 2012.11, we already have enough
issues to fix.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-11 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 12:38 [Buildroot] [PATCH] libtool version update 2.4.2 Alexander Khryukin
2012-11-10 9:53 ` Thomas Petazzoni
2012-11-10 16:31 ` Alexander Khryukin
2012-11-11 22:00 ` Arnout Vandecappelle
2012-11-11 22:05 ` Thomas Petazzoni [this message]
2012-11-12 7:46 ` Stephan Hoffmann
2012-11-12 10:18 ` Alexander Khryukin
2012-11-12 10:26 ` Thomas Petazzoni
2012-11-12 20:57 ` 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=20121111230546.709735e3@skate \
--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 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.