From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from smtprelay03.ispgateway.de ([80.67.29.28])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <bernhard@bwalle.de>) id 1RFkhG-0008Mp-0L
	for ptxdist@pengutronix.de; Mon, 17 Oct 2011 12:45:31 +0200
Received: from [78.47.165.117] (helo=regiomontanus.bwalle.de)
	by smtprelay03.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128)
	(Exim 4.68) (envelope-from <bernhard@bwalle.de>) id 1RFkhE-0004M4-EU
	for ptxdist@pengutronix.de; Mon, 17 Oct 2011 12:45:28 +0200
Date: Mon, 17 Oct 2011 12:45:26 +0200
From: Bernhard Walle <bernhard@bwalle.de>
Message-ID: <20111017104526.GA25269@regiomontanus.bwalle.de>
References: <1317833666-11917-1-git-send-email-andreas@biessmann.de>
	<1318262696-584-1-git-send-email-m.olbrich@pengutronix.de>
	<8d386ec882c49464e95a77a4f92dc68b@biessmann.de>
	<20111014140434.GE4886@pengutronix.de>
	<20111014150343.GA31488@regiomontanus.bwalle.de>
	<8827b632aa90795542df9b3ef705367b@biessmann.de>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <8827b632aa90795542df9b3ef705367b@biessmann.de>
Subject: Re: [ptxdist] [PATCH] libptxdist: explicitly use sed to run
	migrate_*
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de

* Andreas Bie=DFmann <andreas@biessmann.de> [2011-10-17 09:06]:
> =

> >It's not really nice, but I think it's better than patching lots of
> >tools. And having scripts as executable programs is IMO still better
> >than having to call the interpreter manually (which is necessary with
> >your $PTXDIST_SED approach.
> =

> But how should we handle a script's sheebang? If we require the
> scripts/migrate tools to be executable scripts we need to preprocess
> the scripts to adopt the sheebang to e.g. $PTXDIST_BINDIR. I think
> it is much more portable to have the shell scripts kall the
> interpreter with the respective configuration, e.g.
> $PTXDIST_BINDIR/sed -f scripts/migrate/migrate_platform.

sed is the only exception I know that requires an argument.
#!/usr/bin/env perl, #!/usr/bin/env python, #!/usr/bin/env ruby works.


Regards,
Bernhard

-- =

ptxdist mailing list
ptxdist@pengutronix.de