From owner-freebsd-ports@FreeBSD.ORG Tue Jun 11 19:03:19 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B87AECA0 for ; Tue, 11 Jun 2013 19:03:19 +0000 (UTC) (envelope-from jamebus@gmail.com) Received: from mail-vc0-f173.google.com (mail-vc0-f173.google.com [209.85.220.173]) by mx1.freebsd.org (Postfix) with ESMTP id 7D9AE16C5 for ; Tue, 11 Jun 2013 19:03:19 +0000 (UTC) Received: by mail-vc0-f173.google.com with SMTP id ht10so2158777vcb.32 for ; Tue, 11 Jun 2013 12:03:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=eYEN9Xo38NIGCCjnP9BDWkaIHhk/e18LnCPUtILwoo4=; b=q6s+CDxx8fKPYk5YdjVhqBfZgRWJLkJP1rUzaMcKu+76eBtWA1c2mkf4C/RjshfGCs LzZ2RL6SQDxzEIEyFnMQ6Jr26cNw3rU5lpQWEaRSsuKef0+EQj44FlG1UCP+T+pzX/fT NDDeu/hii8/96jYphy2UWl43KIjHig8CbHcAUxDdDJDz5QtMJhzFAhG/t9KDrXN3dK+J IT4+Oo1rdZgdMmRXXqCkSDmVdDAjMWqUgYufqdeEpG9tK9rmXWVnwgF0P4Y0+d56UQit Z5sDw1RevGSy2gPJjKElTEYYDpwjBPGa4oJd3oCrDZXtJL76xcdGadIlFBZb3D6XPmKu fvxA== MIME-Version: 1.0 X-Received: by 10.220.248.137 with SMTP id mg9mr8484138vcb.38.1370977393557; Tue, 11 Jun 2013 12:03:13 -0700 (PDT) Sender: jamebus@gmail.com Received: by 10.58.230.137 with HTTP; Tue, 11 Jun 2013 12:03:13 -0700 (PDT) In-Reply-To: <20130611131221.3a222e13@scorpio> References: <71c953f9ebbd220a72258fb1dbf322f8.squirrel@mouf.net> <20130611131221.3a222e13@scorpio> Date: Tue, 11 Jun 2013 14:03:13 -0500 X-Google-Sender-Auth: _zJcNbgN7tOgV5E3qHl1Pa36R7M Message-ID: Subject: Re: www/rubygem-passenger now requires bash? From: James To: FreeBSD-ports Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2013 19:03:19 -0000 On Tue, Jun 11, 2013 at 12:12 PM, Jerry wrote: > I totally agree. Plus, perhaps the port can be modified to use "env" > to locate bash; ie, "\usr\bin\env bash". I use it all the time for > shell scripts that I write for various systems and it hasn't failed > me yet. Aye. bapt@ is working on a solution for this. I'm not sure where it's at right now, but it looks really handy. He's proposing a framework that automatically fixes the path in shebangs. It's less fragile than env(1) when dealing with daemons=97those start up with a stock path unless you change /etc/rc or related. I run into this problem sometimes too. I build ports to a non-standard prefix so anything that hard-codes /usr/local is apparent. :) At the moment I patch or substitute the scripts which works fine, but bapt's solution is better. -- James.