From owner-freebsd-hackers  Thu Jul 20 13:37:35 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id NAA22150
          for hackers-outgoing; Thu, 20 Jul 1995 13:37:35 -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 NAA22142
          for <hackers@freebsd.org>; Thu, 20 Jul 1995 13:37:32 -0700
Received: (from asami@localhost) by forgery.CS.Berkeley.EDU (8.6.11/8.6.9) id NAA02882; Thu, 20 Jul 1995 13:37:18 -0700
Date: Thu, 20 Jul 1995 13:37:18 -0700
Message-Id: <199507202037.NAA02882@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: <199507202028.NAA09723@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

 * Actually it has a bug too, it assumes src and ports are sitting
 * side by side.  I caught this when you pointed on the symlink
 * from /usr/src/ports -> /usr/ports or where ever it may be.
 * 
 * DO NOT apply my patch, it is not a general solution to the
 * problem :-(.  And infact for anyone who has symlinked /usr/src
 * off some place will probably be the wrong solution :-(.
 * 
 * Need more time to think about this to see if I can come up with
 * a real solution.  Any ideas???

That's right, many people have /usr/src -> /a/src and /usr/ports ->
/b/ports kinds of setups.

The only way to "solve" this is to use the full pathname "/usr/ports"
in there, but then it will screw up people who have src and ports side 
by side on a separate location.

I'd prefer it nuked, it just doesn't belong here.

Satoshi