From owner-freebsd-hackers  Wed Jul 19 17:43:36 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id RAA20062
          for hackers-outgoing; Wed, 19 Jul 1995 17:43:36 -0700
Received: from forgery.CS.Berkeley.EDU (forgery.CS.Berkeley.EDU [128.32.33.75])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id RAA20050
          for <hackers@freebsd.org>; Wed, 19 Jul 1995 17:43:35 -0700
Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id RAA01960; Wed, 19 Jul 1995 17:43:29 -0700
Date: Wed, 19 Jul 1995 17:43:29 -0700
Message-Id: <199507200043.RAA01960@forgery.CS.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: hackers@freebsd.org
In-reply-to: <20363.806200231@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: Strange entries in /usr/src/Makefile
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: hackers-owner@freebsd.org
Precedence: bulk

 * These were done on behalf of Julian Stacey, who wanted some sort of
 * tighter integration in his "really build the world" makes.  Myself,
 * I think it's cruft and it should go.  If you want to build the world,
 * a small shell script does fine:

I agree with you, this is just confusing.  (I received a question
"should I put the ports lndir in /usr/src/ports?" from a user who took
a long hard look into /usr/src/Makefile.)  More importantly, it
directly conflicts with bsd.port.mk, which has the ports in /usr/ports
by default.

A funny shell script like yours or a command line with a "cd" in it
(don't tell me you don't know how to do that, Julian :) should do just
fine.

Satoshi