From owner-freebsd-ports  Tue Jul 28 10:22:58 1998
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA25674
          for freebsd-ports-outgoing; Tue, 28 Jul 1998 10:22:58 -0700 (PDT)
          (envelope-from owner-freebsd-ports@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25465;
          Tue, 28 Jul 1998 10:21:36 -0700 (PDT)
          (envelope-from obrien@FreeBSD.org)
From: "David E. O'Brien" <obrien@FreeBSD.ORG>
Received: (from obrien@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id KAA04774;
	Tue, 28 Jul 1998 10:20:14 -0700 (PDT)
Date: Tue, 28 Jul 1998 10:20:14 -0700 (PDT)
Message-Id: <199807281720.KAA04774@freefall.freebsd.org>
To: Jos.Vissers@usquebaugh.telebyte.nl, obrien@FreeBSD.ORG,
        freebsd-ports@FreeBSD.ORG
Subject: Re: ports/7256
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: different ports installing binaries with same name/location

State-Changed-From-To: open-closed
State-Changed-By: obrien
State-Changed-When: Tue Jul 28 10:19:05 PDT 1998
State-Changed-Why: 
We have many, many cases of conflicts of file names w/in the ports collection.
We have yet to find a solution that is tolerable.  (sugguestions welcomed
of course).  Until we hav such a solution, I guess we just have to live with
the current situation.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message