From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v2 2/3] package/perl-crypt-openssl-random: bump version to 0.15
Date: Tue, 21 Aug 2018 22:49:55 +0200 [thread overview]
Message-ID: <20180821224955.58358a40@windsurf> (raw)
In-Reply-To: <20180821204134.2819-2-bernd.kuhls@t-online.de>
Hello,
On Tue, 21 Aug 2018 22:41:33 +0200, Bernd Kuhls wrote:
> Changelog:
> https://metacpan.org/changes/distribution/Crypt-OpenSSL-Random
>
> Added new build dependency to host-perl-crypt-openssl-guess and force
> it to search for openssl in STAGING_DIR. Added license hash.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> v2: switched to host version of perl-crypt-openssl-guess (Thomas)
It would be nice if you could *reply* to the review e-mails that are
being sent to you. Indeed, I'd like to have more explanation about this.
How is it possible that your previous iteration, which was adding
perl-crypt-openssl-guess as a *target* package could be working ?
Thmas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-21 20:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 20:41 [Buildroot] [PATCH/next v2 1/3] package/perl-crypt-openssl-guess: new package Bernd Kuhls
2018-08-21 20:41 ` [Buildroot] [PATCH/next v2 2/3] package/perl-crypt-openssl-random: bump version to 0.15 Bernd Kuhls
2018-08-21 20:49 ` Thomas Petazzoni [this message]
2018-09-12 14:39 ` Thomas Petazzoni
2018-09-13 6:09 ` Bernd Kuhls
2018-08-21 20:41 ` [Buildroot] [PATCH/next v2 3/3] package/perl-crypt-openssl-rsa: bump version to 0.30 Bernd Kuhls
2018-08-23 9:49 ` [Buildroot] [PATCH/next v2 1/3] package/perl-crypt-openssl-guess: new package Thomas Petazzoni
[not found] ` <dec5946c-8c4e-0075-62a3-251daf7cb856@t-online.de>
2018-09-13 12:33 ` [Buildroot] [PATCH/next v2 2/3] package/perl-crypt-openssl-random: bump 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=20180821224955.58358a40@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 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.