From owner-freebsd-ports  Fri Apr  7 04:05:08 1995
Return-Path: ports-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id EAA03374
          for ports-outgoing; Fri, 7 Apr 1995 04:05:08 -0700
Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.RWTH-Aachen.DE [134.130.90.6])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA03277
          ; Fri, 7 Apr 1995 04:04:05 -0700
Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.6.8/8.6.6) id NAA06074; Fri, 7 Apr 1995 13:03:51 +0200
From: Thomas Gellekum <thomas@ghpc8.ihf.rwth-aachen.de>
Message-Id: <199504071103.NAA06074@ghpc6.ihf.rwth-aachen.de>
Subject: Re: Portsmeister!
To: jkh@freefall.cdrom.com (Jordan K. Hubbard)
Date: Fri, 7 Apr 1995 13:03:51 +0200 (MET DST)
Cc: asami@freefall.cdrom.com, ports@freefall.cdrom.com
In-Reply-To: <199504070936.CAA00414@freefall.cdrom.com> from "Jordan K. Hubbard" at Apr 7, 95 02:36:51 am
Organization: Institut f. Hochfrequenztechnik, RWTH Aachen
X-Mailer: ELM [version 2.4 PL23]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 540       
Sender: ports-owner@FreeBSD.org
Precedence: bulk

Jordan K. Hubbard wrote:
> How about 2 new features:
> 
> 1. files/post-build
> 
> If this file exists then we execute it as a script (I'd like this as
> the default action for the post-build target, anyway).

How about post-install? One example is elk, where I changed the
install target to move some files out of /usr/local/lib/elk/... to
more appropriate places. I preferred like this rather than patching
some of elk's own installation scripts which may change. A
post-install target could catch those situations much more cleanly.

tg