Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
Organization: convey Information Systems GmbH
To: cygwin-apps AT cygwin DOT com
Date: Tue, 28 Aug 2001 19:07:48 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Updated setup.ini with descriptions, categories, and dependencies
Message-ID: <3B8BEC04.663.1C93E90@localhost>
In-reply-to: <20010828112714.A22388@redhat.com>
References: <20010828150605 DOT F25382 AT cygbert DOT vinschen DOT de>
X-mailer: Pegasus Mail for Win32 (v3.12cDE)

> Christopher Faylor schrieb am 2001-08-28 11:27:

>As I mentioned, I am going to be sticking with the RPM descriptions.
>
>The categories are a little more problematic.  I don't agree with them in
>some cases, but I was hoping to write a general purpose tool which generated
>dependencies and categories from RPM.  If every single package is a special
>case, then the tool isn't very useful.
>
>I don't mind trashing the tool but I'd like to understand why the RPM
>categories are not acceptable.

Why not use easier categories like they do in slackare?
They got 15 categories plus 'source' and 'contrib' where all the rest 
lies, e.g. gcc-3.0 for the brave.
Many will not be needed for cygwin (x, kde, gtk, maybe in future?). 

Some programs may also reside in two or more categories to find them
easier like cvs that i put (as a demo) in 'devel' and in 'net'.
Setup knows where the package is so there is no problem if one package
contains both, the runtime and the devel part of something.

As i see now, cygwin is really a development platform:
======================================================
a:
==
ash, bash, bzip2, cpio, cygrunsrv, cygwin, fileutls, find, grep, gzip, 
hello, login, sh-utils, tar, tcsh, txtutils, util,  

ap:
===
clear, cron, diff, file, ghostscript, groff, gsfonts, less, man, 
manpages, mt, rxvt, texinfo, time, unzip, vim, which, zip

d:
==
autoconf, automake, binutils, bison, byacc, ctags, crypt, cvs, dejagnu,
flex, gawk, gcc, gcc_g77, gcc_objc, gdb, gdbm, gettext, gpref, jbigkit, 
jpeg6, libpng, libtiff, libtool, m4, make, ncurses, opengl, patch, pcre,
perl, popt, python, readline, regex, sed, strace, termcap, w32api, xpm,
xpm-nox, zlib

e:
==
no emacs

faqs:
=====
howtos, manyfaqs, minis, newlibman, docs

gnome:
======
no gnome

k:
==
what the hell is k;)

kde:
====
no kde

net:
====
cvs, lynx, mutt, ncftp, openssh, openssl, rsync, ssmtp, wget

t:
==
tetex, (tex_bin, tex_doc, transfig, xfig)

tcl:
====
expect, tcl, tix, tk

x, xap, xv: 
===========
no X (yet)

y:
==
games, contribs like: irc, mingw, postgresql, squid

Ciao,

Gerrit


-- 
gerrit DOT haase AT convey DOT de