Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Subject: Re: Updated setup.ini with descriptions, categories, and dependencies From: Robert Collins To: cygwin-apps AT cygwin DOT com Cc: cygwin-developers AT cygwin DOT com In-Reply-To: <20010828112714.A22388@redhat.com> References: <20010827004327 DOT A14852 AT redhat DOT com> <20010828134119 DOT A25382 AT cygbert DOT vinschen DOT de> <2022197257 DOT 20010828160649 AT logos-m DOT ru> <20010828142656 DOT C25382 AT cygbert DOT vinschen DOT de> <9824009784 DOT 20010828163702 AT logos-m DOT ru> <20010828150605 DOT F25382 AT cygbert DOT vinschen DOT de> <20010828112714 DOT A22388 AT redhat DOT com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.12 (Preview Release) Date: 29 Aug 2001 11:55:27 +1000 Message-Id: <999050129.28151.8.camel@robertlinux> Mime-Version: 1.0 X-OriginalArrivalTime: 29 Aug 2001 01:56:31.0408 (UTC) FILETIME=[D2F5F300:01C1302D] On 28 Aug 2001 11:27:14 -0400, Christopher Faylor wrote: > I don't mind trashing the tool but I'd like to understand why the RPM > categories are not acceptable. Some of them are accurate-but-misleading. Take squid for instance. Yes it is a daemon.. but its much more intuitive (for me) to look for it as a "Net" item. > WRT, breaking up cygwin into two packages, I think that that would just be > busy work. It would complicate my life to do this and I think it would > complicate all of our lives when the questions start cropping up on the > mailing list. I agree. Somehow my rename it to libcygwin got lost however - what are your thoughts on that? (the goal being removing the current cygwin-the-distro, cygwin-the-project, cygwin-the-package) confusion somewhat by making it (cygwin-the-distro, cygwin-the-project, libcygwin-the-package). > Ditto, ssh. I've never liked the server/client distinction in RPM. I'd > rather just keep ssh as one package. Splitting _can_ have some benefits in terms of being able to do more lightweight installs for non-development machines. Server/client splitting IMO doesn't usually bring those benefits. And IMO the project really isn't big enough to needs such splits (yet). Rob