From: Bernhard Walle <bernhard@bwalle.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libptxdist: explicitly use sed to run migrate_*
Date: Mon, 17 Oct 2011 12:45:26 +0200 [thread overview]
Message-ID: <20111017104526.GA25269@regiomontanus.bwalle.de> (raw)
In-Reply-To: <8827b632aa90795542df9b3ef705367b@biessmann.de>
* Andreas Bießmann <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
next prev parent reply other threads:[~2011-10-17 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 7:33 [ptxdist] [PATCH] scripts/migrate: use env to find sed Andreas Bießmann
2011-10-04 13:26 ` Michael Olbrich
2011-10-05 16:54 ` [ptxdist] [PATCH v2] scripts/migrate: use autotools to insert working sed Andreas Bießmann
2011-10-10 16:04 ` [ptxdist] [PATCH] libptxdist: explicitly use sed to run migrate_* Michael Olbrich
2011-10-11 10:16 ` andreas
2011-10-14 14:04 ` Michael Olbrich
2011-10-14 15:03 ` Bernhard Walle
2011-10-17 7:06 ` Andreas Bießmann
2011-10-17 10:45 ` Bernhard Walle [this message]
2011-10-17 12:53 ` Michael Olbrich
2011-10-17 6:54 ` Andreas Bießmann
2011-10-17 7:10 ` Andreas Bießmann
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=20111017104526.GA25269@regiomontanus.bwalle.de \
--to=bernhard@bwalle.de \
--cc=ptxdist@pengutronix.de \
/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