From owner-freebsd-ports  Sat Dec 13 18:16:34 1997
Return-Path: <owner-freebsd-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA13537
          for ports-outgoing; Sat, 13 Dec 1997 18:16:34 -0800 (PST)
          (envelope-from owner-freebsd-ports)
Received: from baloon.mimi.com (sjx-ca124-26.ix.netcom.com [207.223.162.154])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13469;
          Sat, 13 Dec 1997 18:16:25 -0800 (PST)
          (envelope-from asami@sunrise.cs.berkeley.edu)
Received: (from asami@localhost)
	by baloon.mimi.com (8.8.8/8.8.8) id SAA14030;
	Sat, 13 Dec 1997 18:16:23 -0800 (PST)
	(envelope-from asami)
Date: Sat, 13 Dec 1997 18:16:23 -0800 (PST)
Message-Id: <199712140216.SAA14030@baloon.mimi.com>
To: jkh@freebsd.org
CC: ports@freebsd.org
Subject: the infodist problem
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-freebsd-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Jordan,

Will it ruffle too many feathers if we take /usr/share/info/dir out of
infodist and put it in bindist?  Or even better, put a skeleton
version (no entries, just headers) in bindist.

Many people are stumbling on this when they install ports that require
info dir entries to be installed.  I can't think of any other way to
solve this.  (We surely don't want a "info-dir" port just for this
purpose!)

Satoshi