From owner-freebsd-hackers Thu Jul 20 14:14:24 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id OAA24546 for hackers-outgoing; Thu, 20 Jul 1995 14:14:24 -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 OAA24539 for ; Thu, 20 Jul 1995 14:14:22 -0700 Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id OAA02916; Thu, 20 Jul 1995 14:14:17 -0700 Date: Thu, 20 Jul 1995 14:14:17 -0700 Message-Id: <199507202114.OAA02916@forgery.CS.Berkeley.EDU> To: rgrimes@gndrsh.aac.dev.com CC: jhs@vector.eikon.e-technik.tu-muenchen.de, jkh@time.cdrom.com, hackers@freebsd.org In-reply-to: <199507202103.OAA09826@gndrsh.aac.dev.com> (rgrimes@gndrsh.aac.dev.com) Subject: Re: Strange entries in /usr/src/Makefile From: asami@cs.berkeley.edu (Satoshi Asami) Sender: hackers-owner@freebsd.org Precedence: bulk * > I'd prefer it nuked, it just doesn't belong here. * * Then neither does the assumption in bsd.ports.mk that /usr/ports is * the root of the ports tree :-(. That is after all what started this * whole thread, that bsd.port.mk and /usr/src/Makefile where in disagreement * about locations. bsd.ports.mk does not assume that the ports tree is located at /usr/ports, it is just the default and can be changed by PORTSDIR. (Or, more precisely, PORTSDIR is set to /usr/ports in bsd.ports.mk if not defined by the user, and that's the root of the ports tree.) If we read bsd.port.mk from /usr/src/Makefile *before* the lines in question, we can use PORTSDIR to build the ports as part of make world. But we don't. Can I nuke them please? The main source tree and the ports tree are two different beasts, it just doesn't make much sense to assume anything about where they should be on a user's machine. Especially if the "problem" can be solved by a 2-line shell script or a shell command with three semicolons. Satoshi