Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] package/rng-tools: bump to 6.7
Date: Wed, 11 Sep 2019 09:47:23 +0200	[thread overview]
Message-ID: <20190911094723.3599082f@windsurf> (raw)
In-Reply-To: <20190910203902.5852-2-matthew.weber@rockwellcollins.com>

On Tue, 10 Sep 2019 15:39:02 -0500
Matt Weber <matthew.weber@rockwellcollins.com> wrote:

> * Add new libsysfs dependency for rng available check
> * Remove patch adding special return code when no RNG module is available
> * Remove exit code corner case in systemd script
> * Add new jitterentropy dependency which always provides a entropy source
> * Change to a autotools build
> * Switch to new site and add license file hash
> 
> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com>
> ---
> Changes v1 -> v2
> [Thomas P
>  - Added host automake/autotools dependencies and checked for no
>    libtool dependency.

As I replied to your v1 just a few minutes ago, if the issue with
<pkg>_AUTORECONF = YES is just the README being missing, then there's a
simple and good solution of adding the "foreign" argument to
AM_INIT_AUTOMAKE. This should be a simple upstreamable patch.

Of course, for upstreaming, you can drop the line in autogen.sh that
copies README.md into README.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-09-11  7:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-10 20:39 [Buildroot] [PATCH v2 1/2] package/jitterentropy-library: new package Matt Weber
2019-09-10 20:39 ` [Buildroot] [PATCH v2 2/2] package/rng-tools: bump to 6.7 Matt Weber
2019-09-11  7:47   ` 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=20190911094723.3599082f@windsurf \
    --to=thomas.petazzoni@bootlin.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