From owner-freebsd-ports  Thu Jun  5 21:31:14 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA25942
          for ports-outgoing; Thu, 5 Jun 1997 21:31:14 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA25936
          for <freebsd-ports@freebsd.org>; Thu, 5 Jun 1997 21:31:11 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id TAA29551; Thu, 5 Jun 1997 19:46:27 -0700 (PDT)
Date: Thu, 5 Jun 1997 19:46:27 -0700 (PDT)
Message-Id: <199706060246.TAA29551@silvia.HIP.Berkeley.EDU>
To: rssh@cki.ipri.kiev.ua
CC: freebsd-ports@freebsd.org
In-reply-to: <3396E575.217C@cki.ipri.kiev.ua> (message from Ruslan Shevchenko on Thu, 05 Jun 1997 19:12:33 +0300)
Subject: Re: ports/3757
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-ports@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Now about the other half:

 * And about general port structure:
 *   may be we must have LINKS future: i.e. allow ports to
 * be not well-ordered by depends (in algebraick sense), and run
 * from crom stuff, which see: if new ports adeed ? --- may be linked
 * from existings ports and so on.
 * 
 *  Examples, way we need in this:
 * 
 *    1. TeX styles, (we must link it in texfmt directory, and,
 * in case teTeX rerun texhush)
 *    2. .el files (when adding emacs/xemacs)
 *    
 *  May be we must create some stuff, as windows registry, which
 * holds the name of actions and variable.
 * (And allow read envirowment variables to shell during boot)
 * 
 * P.S. I cc:-ed his to freebsd-ports, to stimulate discussion about
 *       this.

Sorry, I have no idea what you are talking about here. ;)

Satoshi