From owner-freebsd-ports  Thu Mar 30 04:00:45 1995
Return-Path: ports-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA24948 for ports-outgoing; Thu, 30 Mar 1995 04:00:45 -0800
Received: from nietzsche (annex1s34.urc.tue.nl [131.155.12.44]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA24922; Thu, 30 Mar 1995 04:00:30 -0800
Received: from localhost (localhost [127.0.0.1]) by nietzsche (8.6.9/8.6.9) with ESMTP id NAA07404; Thu, 30 Mar 1995 13:18:28 +0200
Message-Id: <199503301118.NAA07404@nietzsche>
X-Mailer: exmh version 1.5.3 12/28/94
To: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
cc: asami@cs.berkeley.edu (Satoshi Asami/=?ISO-2022-JP?B?GyRCQHUbKEI=?=
    =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?=),
        ports@FreeBSD.org
Subject: Re: Let's make the packages/ dir look clean! 
In-reply-to: Your message of "Wed, 29 Mar 1995 12:37:57 -0800."
             <28421.796509477@freefall.cdrom.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 30 Mar 1995 13:18:27 +0200
From: "wmbfmk@urc.tue.nl" <wmbfmk@urc.tue.nl>
Sender: ports-owner@FreeBSD.org
Precedence: bulk

> > My suggestion is that package names should be the format
> > 
> > <name>-<major>[.<minor>[.<patchlevel>]].tgz
> 
> This sounds good to me, though I might ask whether or not it would also
> pay dividends if we were to seize this opportunity to CATAGORIZE the
> packages at the same time.  We should come up with a <pkgdir>/<catagory>
> scheme where the packages are dumped according to where they came from
> in the ports hierarchy.  Using a LINKS type of scheme, it should also
> be possible for a package to link itself into multiple catagories
> and thus provide a de-facto "ueberpackage" scheme like Paul T. was
> talking about - my installation program can just get the top level
> directory names (some of which will represent ports catagories and
> some which won't) and show the various packages within it as the
> contents of the ueberpackage.
> 
Could there also be a scheme to make packages possible,
which will group applications not on where they came from but to 
targets usable for a specific purpose.

Examples would be:

	net-package
		-web browser	
		-communication program (Seyon, minicom)
		-mail front end
		-news reader
		-pop client
		
	"FreeBSD-Works" :-)
		-tex
		-ispell
		-tgif
		-xspread
		-database program
		...
	etc.

These could be directories containing links to applications elsewhere
in the packages tree.

Marc.