From: Andrea Bolognani <abologna@redhat.com>
To: John Snow <jsnow@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: minimal "zero conf" build dockerfiles for fedora:latest and alpine:latest
Date: Thu, 14 Jan 2021 12:10:50 +0100 [thread overview]
Message-ID: <a232018c476425641f8dbf2f8edfcb37a3313054.camel@redhat.com> (raw)
In-Reply-To: <88f80fb6-62ad-77ca-4047-b1c79fd6a006@redhat.com>
On Wed, 2021-01-13 at 13:31 -0500, John Snow wrote:
> On 1/13/21 5:09 AM, Gerd Hoffmann wrote:
> > > I don't like Perl really, but there's a chicken-and-egg problem between
> > > detecting Python and using it to print the configure help script. For
> > > configure-time tasks, Perl has the advantage that "#! /usr/bin/env perl"
> > > just works.
> >
> > Assuming perl is actually installed, the world seems to shift to python.
> > On a minimal fedora install python is present but perl is not ...
> >
> > On the other hand git depends on perl, so it is probably pretty hard to
> > find a developer workstation without perl installed, so maybe that
> > doesn't matter much for the time being.
>
> I agree that it doesn't matter much right now, Though I don't always
> have git installed in containers when I am doing builds. It will become
> more common to encounter environments that are missing "obvious"
> dependencies.
Note that Fedora has a git-core package that doesn't depend on Perl
while still providing more than enough git for something like a CI
build job.
As a data point, the libvirt project has made it an explicit goal[1]
to remove all usage of Perl in favor of Python. We're not quite there
yet, but at this point there are only a very tiny handful of Perl
scripts remaining in the repository.
[1] https://libvirt.org/strategy.html
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2021-01-14 11:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:37 minimal "zero conf" build dockerfiles for fedora:latest and alpine:latest John Snow
2021-01-13 6:48 ` Thomas Huth
2021-01-13 8:26 ` Paolo Bonzini
2021-01-13 10:09 ` Gerd Hoffmann
2021-01-13 10:29 ` Philippe Mathieu-Daudé
2021-01-13 14:35 ` Paolo Bonzini
2021-01-13 18:31 ` John Snow
2021-01-14 11:10 ` Andrea Bolognani [this message]
2021-01-14 16:13 ` John Snow
2021-01-13 18:27 ` John Snow
2021-01-13 8:20 ` Paolo Bonzini
2021-01-13 18:44 ` John Snow
2021-01-14 16:51 ` Philippe Mathieu-Daudé
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=a232018c476425641f8dbf2f8edfcb37a3313054.camel@redhat.com \
--to=abologna@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jsnow@redhat.com \
--cc=kraxel@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).