From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] scancpan: fix doc
Date: Tue, 14 Jun 2016 21:58:10 +0200 [thread overview]
Message-ID: <20160614195810.GD3759@free.fr> (raw)
In-Reply-To: <1465930064-19189-1-git-send-email-francois.perrad@gadz.org>
Fran?ois, All,
On 2016-06-14 20:47 +0200, Francois Perrad spake thusly:
> we need to install a host perl with the same version as our target perl
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
> ---
> support/scripts/scancpan | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/support/scripts/scancpan b/support/scripts/scancpan
> index 6c70cfb..c2aa2e9 100755
> --- a/support/scripts/scancpan
> +++ b/support/scripts/scancpan
> @@ -748,7 +748,7 @@ support/scripts/scancpan Try-Tiny Moo
>
> curl -kL http://install.perlbrew.pl | bash
>
> -perlbrew install perl-5.18.2
> +perlbrew install perl-5.22.2
Would it be possible that, if this requirement is not met, it exits
with an informative message instead of just bailing out?
That information message could possibly state something like:
The same version of perl (5.022) as used by Buildroot is not
available on your machine.
You may install a local one by running:
perlbrew install perl-5.22.2
Note however that my installtion (Ubuntu 16.04) is missing perlbrew; it
is not installed by default.
I am not sure where to go from here. On one side, I thing people dealing
with perl would already have such things installed (or be willing to
install them) on their machine.
On the other hand, we've always tried to keep Buildroot's requirement on
the host as minimal as possible, and perlbrew would be adding yet
another dependency.
I'm undecided. But I'd really like the error message, above! ;-)
Regards,
Yann E. MORIN.
> supports/scripts/scancpan [options] [distname ...]
>
> --
> 1.9.1
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2016-06-14 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 18:47 [Buildroot] [PATCH] scancpan: fix doc Francois Perrad
2016-06-14 19:58 ` Yann E. MORIN [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=20160614195810.GD3759@free.fr \
--to=yann.morin.1998@free.fr \
--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