From owner-freebsd-ports  Fri Jan  3 03:37:31 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id DAA14965
          for ports-outgoing; Fri, 3 Jan 1997 03:37:31 -0800 (PST)
Received: from dfw-ix1.ix.netcom.com (dfw-ix1.ix.netcom.com [206.214.98.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA14949
          for <ports@freebsd.org>; Fri, 3 Jan 1997 03:37:29 -0800 (PST)
Received: from silvia.HIP.Berkeley.EDU (ala-ca9-50.ix.netcom.com [207.93.143.114]) by dfw-ix1.ix.netcom.com (8.6.13/8.6.12) with ESMTP id DAA02018; Fri, 3 Jan 1997 03:36:55 -0800
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.4/8.6.9) id DAA01405; Fri, 3 Jan 1997 03:36:51 -0800 (PST)
Date: Fri, 3 Jan 1997 03:36:51 -0800 (PST)
Message-Id: <199701031136.DAA01405@silvia.HIP.Berkeley.EDU>
To: thomas@ghpc8.ihf.rwth-aachen.de
CC: ports@freebsd.org, chuckr@glue.umd.edu
In-reply-to: <199701030714.IAA28561@ghpc6.ihf.rwth-aachen.de> (message from Thomas Gellekum on Fri, 3 Jan 1997 08:14:48 +0100 (MET))
Subject: Re: cvs commit:  ports/x11/tix/patches etc.
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

 * I have a quick fix for this: in the pre-extract target, I could do a
 * test on ${PORTSDIR}/x11/tk41/work/${CONFIGURE_COOKIE} and conditionally
 * `make configure' (and maybe delete one diff in patches/patch-aa).

You can just "make configure", it won't run if the cookie is already
there. :)

 * Yup. Tix defines its own ${INSTALL_PROGRAM} depending on some tests
 * from configure. I added the `-'.

I wish those tests would see if you can strip a script.... :(

 * It needs some internal headers from Tk. I found the internal Tcl
 * headers in /usr/include/tcl; if the Tk port would install all its headers
 * in a similar way (${PREFIX}/include/tk maybe) I could probably get rid
 * of the pre-extract target as a whole.

I'll bounce this to the ports list.  I have no problem with this, in
fact I proposed this a long time ago but some people didn't like it.

However, since tcl (in the system) already does this, there is no
reason why tk can't do it as well.

For the location, yes /usr/local/include/tk sounds fine.  If you have
a list of files (and their final destinations, /usr/include/tcl has
two subdirectories), that will be great.

Satoshi