Date: Wed, 1 May 2013 20:21:56 +0100 From: Chris Rees <utisoft@gmail.com> To: Oliver Heesakkers <freebsd@heesakkers.info> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: [BRAINSTORM] shebang fixing framework Message-ID: <CADLo838bv%2B_4utPFEzHHPsR3n-vtx%2BdHyseXo6eW%2BcbH9F%2BH%2BA@mail.gmail.com> In-Reply-To: <1786370.b1sXK5t6Pv@pcoliver.heesakkers.info> References: <20130430103821.GJ3577@ithaqua.etoilebsd.net> <1786370.b1sXK5t6Pv@pcoliver.heesakkers.info>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1 May 2013 20:18, "Oliver Heesakkers" <freebsd@heesakkers.info> wrote: > > Op di 30 apr 2013 12:38:21 schreef Baptiste Daroussin: > > Hi all, > > > > For a while now: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/51152we > > are looking for a framework/helpers to help patching scripts shebang so > > that they fit where the interpreters is on FreeBSD. > > > (...) > > In there you wrote a patch using /usr/bin/env. Why not stick with that? I'm > quite fond of this technique as it's clean and portable. > > Portability might not be that important when working on a fix for ports alone, > but still makes sense to me. On the contrary, it teaches good habits to people. Writing portable code also means it's less likely to break. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo838bv%2B_4utPFEzHHPsR3n-vtx%2BdHyseXo6eW%2BcbH9F%2BH%2BA>