From owner-freebsd-commit  Tue Oct 17 13:52:19 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA07421
          for freebsd-commit-outgoing; Tue, 17 Oct 1995 13:52:19 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA07404
          for cvs-all-outgoing; Tue, 17 Oct 1995 13:52:10 -0700
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA07394
          for cvs-ports-outgoing; Tue, 17 Oct 1995 13:52:04 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id NAA07384
          ; Tue, 17 Oct 1995 13:51:50 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.12/8.6.9) id NAA08719; Tue, 17 Oct 1995 13:49:33 -0700
Date: Tue, 17 Oct 1995 13:49:33 -0700
Message-Id: <199510172049.NAA08719@silvia.HIP.Berkeley.EDU>
To: ache@astral.msk.su
CC: CVS-commiters@freebsd.org, cvs-ports@freebsd.org
In-reply-to: <jlZ11Xmmu7@ache.dialup.demos.ru>
Subject: Re: cvs commit: ports/audio/tracker/pkg COMMENT
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-commit@freebsd.org
Precedence: bulk

 * > * P.S. Can you do something with the *.language Makefiles?  Will they
 * > *    work if you change all the empty targets to NO_*?
 * 
 * >This doesn't mean you can modify bsd.port.mk at this point of the
 * >game.  During the CONFIGURE_ENV debate, I thought I've been clear
 * 
 * Well, I just follows your words completely, i.e. "change all the empty
 * targets to NO_*", it requires bsd.port.mk changes.

I just ASKED if they will work if you change them, I didn't look at
every one of the targets carefully.  The answer was obviously "no".

 * >enough that I wanted you to fix ports within the ports tree, without
 * >changing bsd.port.mk! :<
 * 
 * Well, you ask me to ask you before I touch bsd.port.mk, I treat your email
 * as direct instructions to do it.

I have no idea why the mail you cited above means you can change
bsd.port.mk, I've been saying from time to time that I intend to keep
tight control on bsd.port.mk (even more so since it's release time
right now).  I give you a hint on how to fix one of the Makefiles and
you treat that as "direct instructions" to change bsd.port.mk?

 * Can you write from time to time more formal and clear descriptions of
 * your plans and announce them to avoid such misunderstanding?

I intend to think it's your fault of not reading carefully enough what
I've said, but you probably think the other way so let's stop this one 
here.

Anyway, I (sort of) agree with your last point, so it's a full freeze
in the ports subtree and bsd.port.mk.  No misunderstandings, right?

Satoshi