From owner-freebsd-ports@FreeBSD.ORG Mon Oct 21 17:30:35 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9778EC30 for ; Mon, 21 Oct 2013 17:30:35 +0000 (UTC) (envelope-from FreeBSD@heesakkers.info) Received: from server4.ohos.nl (server4.ohos.nl [IPv6:2a00:d880:0:6::c951:214d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5CB7A2812 for ; Mon, 21 Oct 2013 17:30:35 +0000 (UTC) Received: from [2001:470:1f15:1555::2] (helo=pcoliver.heesakkers.info) by server4.ohos.nl with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80.1) (envelope-from ) id 1VYJJF-000Nw3-8w for freebsd-ports@freebsd.org; Mon, 21 Oct 2013 19:30:30 +0200 From: Oliver Heesakkers To: freebsd-ports@freebsd.org Subject: Re: Should /usr/bin/perl be a link to /usr/local/bin/perl ? Date: Mon, 21 Oct 2013 19:29:25 +0200 Message-ID: <2009160.jDFQa85PyP@pcoliver.heesakkers.info> User-Agent: KMail/4.10.5 (FreeBSD/9.1-RELEASE-p7; KDE/4.10.5; amd64; ; ) In-Reply-To: <52655AA1.6090304@rawbw.com> References: <52655AA1.6090304@rawbw.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Mon, 21 Oct 2013 17:30:35 -0000 Op ma 21 okt 2013 09:47:29 schreef Yuri: > I found that many ports specify /usr/bin/perl as an interpreter. This > comes from Linux. Examples: valgrind-snapshot, windowmaker, enscript-a4, > a2ps, svgalib > /usr/bin/perl isn't installed by perl port. > > There are several solutions, in the order of increasing complexity of > solution: > 1. Install the link /usr/bin/perl (hackish, but it will fix many broken > ports in one shot) > 2. Make a package scripts check for interpreter and break the install of > offending packages > 3. Fix all offending packages > > Which solution should be preferred in your opinion? > 3b. Teach upstream to write: #!/usr/bin/env perl