public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Rob Landley <rob@landley.net>,
	linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
	Arnd Bergmann <arnd@arndb.de>,
	Cyrill Gorcunov <gorcunov@openvz.org>,
	Dave Jones <davej@redhat.com>, David Howells <dhowell@redhat.com>,
	David Howells <dhowells@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	Josh Boyer <jwboyer@redhat.com>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Sam Ravnborg <sam@ravnborg.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vince Weaver <vincent.weaver@maine.edu>,
	x86@kernel.org, Zheng Yan <zheng.z.yan@intel.com>
Subject: Re: [PATCH 0/3] build linux-next without perl
Date: Thu, 28 Feb 2013 09:44:06 +0100	[thread overview]
Message-ID: <512F18D6.4080104@suse.cz> (raw)
In-Reply-To: <20130227135155.c04453db.akpm@linux-foundation.org>

On 27.2.2013 22:51, Andrew Morton wrote:
> It'll need to be reasonably good motivation, too.  Because not only do
> we need to patch the kernel, we also need to *maintain* its
> perl-freeness and fix up perlisms as they later get added by others.
> 
> (Perhaps one way of doing this would be to disable perl in regular
> builds, so even if a developer has perl installed on his machine, his
> build will still fail when he invokes it.  Add "PERL=/dev/null" to some
> build targets in some manner.)

I don't think we need to go this far. Apparently, there are people who
want to be able to build the kernel without perl, so let's rely on them
to report if perl appears again as a hard build dependency. If these
people lose interest, then after some time we might end up with perl
being required again, but then this by definition won't be a problem for
anyone who cares.

It is like bashisms in shell scripts and Makefile commands. They should
be avoided, but it wasn't until Debian and Ubuntu switched to /bin/sh ->
dash when we started to fix them. Nowadays, the kernel should build file
with a minimal POSIX shell, but we did not need any
SHELL=$(objtree)/scripts/dash to achieve this.

Michal

  parent reply	other threads:[~2013-02-28  8:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-27  5:57 [PATCH 0/3] build linux-next without perl Rob Landley
2013-02-27  5:57 ` [PATCH 1/3] convert mkcapflags.pl to mkcapflags.sh Rob Landley
2013-02-27  5:58 ` [PATCH 2/3] convert timeconst.pl to mktimeconst.c Rob Landley
2013-02-27  5:58 ` [PATCH 3/3] convert headers_install.pl to headers_install.sh Rob Landley
2013-02-28  8:19   ` Michal Marek
2013-03-01  5:07     ` Rob Landley
2013-04-09 10:52     ` Michal Marek
2013-04-11 16:25       ` Rob Landley
2013-04-11 19:20         ` Michal Marek
2013-02-27 21:51 ` [PATCH 0/3] build linux-next without perl Andrew Morton
2013-02-28  4:01   ` Rob Landley
2013-02-28  4:48   ` Rob Landley
2013-02-28  6:47   ` Geert Uytterhoeven
2013-02-28  8:44   ` Michal Marek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-02-27 16:55 John Spencer
2013-02-27 18:53 ` Sam Ravnborg
2013-02-27 19:50   ` John Spencer

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=512F18D6.4080104@suse.cz \
    --to=mmarek@suse.cz \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=davej@redhat.com \
    --cc=dhowell@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=gorcunov@openvz.org \
    --cc=gregkh@suse.de \
    --cc=hpa@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jwboyer@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rob@landley.net \
    --cc=rusty@rustcorp.com.au \
    --cc=sam@ravnborg.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.weaver@maine.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=x86@kernel.org \
    --cc=zheng.z.yan@intel.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