From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] libevent: Use github call & fix patch
Date: Sun, 26 Oct 2014 17:01:44 +0100 [thread overview]
Message-ID: <20141026170144.0aaa3d00@free-electrons.com> (raw)
In-Reply-To: <1413739261-3675-1-git-send-email-maxime.hadjinlian@gmail.com>
Dear Maxime Hadjinlian,
On Sun, 19 Oct 2014 19:21:01 +0200, Maxime Hadjinlian wrote:
> We want to use the github helper since there is not a specific releases
> tarball that we can download, as specified in the manual.
>
> This tarball is generated from the tag, which doesn't contains the
> autotools generated files, we then need to use AUTORECONF.
>
> We want to use the github helper anyway as the current URL use an old
> GitHub feature which was called 'Download' where you could upload files
> along your repositories, theses files were not related to your tags.
>
> This features has been replaced with the 'Release' option where you can
> create a release from a git tag. But these tarball are generated from
> the sources and they don't contains all the generated autotools file.
>
> Since the old URL scheme can be deprecated at any time, we want to
> switch to the new URL scheme, which in the case of libevent, implies
> having to do an AUTORECONF.
>
> The patch that was already present is updated to apply against
> Makefile.am instead of Makefile.in
>
> The second patch is backported from upstream to remove the use of
> $(top_src_dirs) which makes current autotools error out.
>
> Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com>
Applied, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-10-26 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 17:21 [Buildroot] [PATCH v4] libevent: Use github call & fix patch Maxime Hadjinlian
2014-10-20 16:48 ` Yann E. MORIN
2014-10-26 16:01 ` 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=20141026170144.0aaa3d00@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