From owner-freebsd-current Sat Jun 8 0:47:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from yello.shallow.net (yello.shallow.net [203.18.243.120]) by hub.freebsd.org (Postfix) with ESMTP id 51A9637B401 for ; Sat, 8 Jun 2002 00:47:33 -0700 (PDT) Received: by yello.shallow.net (Postfix, from userid 1001) id A5BD02A73; Sat, 8 Jun 2002 17:47:25 +1000 (EST) Date: Sat, 8 Jun 2002 17:47:25 +1000 From: Joshua Goodall To: current@freebsd.org Subject: Perl wrapper bad Message-ID: <20020608074725.GA45357@roughtrade.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ... when I say "bad" I don't mean in execution. I mean that the idea of a redirecting wrapper for one special program seems to me an architectural wart that shouldn't be pushed on the userbase. Not only does it conflict in style with the existing mailwrapper, but it introduces a DWIM feature without precedent. Using PATH is simply wrong in restricted-path cases. The idea that manually creating a symlink is an insufficient solution is an underestimation of the intelligence of the FreeBSD userbase. Those who think that a generalisation of mailwrapper would be a cleaner solution can try the following *proof-of-concept*: echo 'myperl /usr/local/bin/perl' >> /etc/mail/mailer.conf ln -s /usr/sbin/mailwrapper /usr/bin/myperl /usr/bin/myperl -v This also works for suidperl. Joshua To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message