From owner-freebsd-ports  Tue Nov 19 10:07:31 1996
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA21158
          for ports-outgoing; Tue, 19 Nov 1996 10:07:31 -0800 (PST)
Received: from fps.biblos.unal.edu.co ([168.176.37.11])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA21138;
          Tue, 19 Nov 1996 10:07:02 -0800 (PST)
From: pgiffuni@fps.biblos.unal.edu.co
Received: from localhost by fps.biblos.unal.edu.co (AIX 4.1/UCB 5.64/4.03)
          id AA21914; Tue, 19 Nov 1996 13:13:03 -0500
Date: Tue, 19 Nov 1996 13:13:03 -0500 (EST)
To: Satoshi Asami <asami@freebsd.org>
Cc: ports@freebsd.org
Subject: Re: Are broken ports useful?
In-Reply-To: <199611190620.WAA27201@silvia.HIP.Berkeley.EDU>
Message-Id: <Pine.A41.3.95.961119123142.41942B-100000@fps.biblos.unal.edu.co>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Thanks to everyone!
I tried (1) and then went straight to (3) I dropped the new port for cim
in ftp.freebsd.org/pub/FreeBSD/incoming!

Pedro.

On Mon, 18 Nov 1996, Satoshi Asami wrote:

> 
> There are three ways around this:
> 
> (1) Look at the configure script, see where it defines INSTALL_PROGRAM
>     and patch that to not include -s.  Then in your toplevel Makefile
>     (i.e., /usr/ports/foo/bar/Makefile), add a post-install: target to 
>     strip the real binaries.
> 
> (2) Look at the part in the Makefile.in that is using
>     ${INSTALL_PROGRAM} to install scripts and change that to
>     ${INSTALL} -m 555 or something.
> 
> Note that INSTALL_PROGRAM is passed through the environment to the
> configure script by bsd.port.mk, so configure might be picking that
> up.  If so, (1) won't work.  In which case:
> 
> (3) Add "STRIP=" (with nothing to the right of "=") in your toplevel
>     Makefile.  Then add a post-install: target like in (1).
> 
> Satoshi
>