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
Date: Fri, 23 Mar 2001 09:42:33 EST
X-Mailer: Virtual Access by Atlantic Coast PLC, http://www.atlantic-coast.com/va
Message-Id: <VA.000006ea.0042d415@thesoftwaresource.com>
To: cygwin-apps AT sources DOT redhat DOT com
Subject: Re: setup wishes -- any volunteers
In-Reply-To: <3ABAD1AF.5B48810B@ece.gatech.edu>
From: Brian Keener <bkeener AT thesoftwaresource DOT com>
Reply-To: bkeener AT thesoftwaresource DOT com

Charles S. Wilson wrote:
> That's not what setup is for, altough you're welcome to use it that 
> way.

I disagree.

> The point: your use of setup is a 'neat thing' but is not the primary
> purpose of the tool.  However, none of the changes folks have been
> discussing will prevent your use of the tool in that way.

I don't know why - I can't put my finger on it but that statement really 
hurts and touched a nerve - my apologies up front

<Getting on soapbox>

Obviously, I missed the boat somewhere - I thought my use of setup was 
exactly the use of setup:  

To allow someone the ability to see what packages are available, to 
download them and/or install them right then or later and not have to be 
concerned with all the knowledge and commands required to do the ftp, the 
tars and so on that would be required without setup.  Then also to 
provide a tool for keeping these packages updated as they should be.  As 
volunteer software it does exactly what it should do and I think what it 
was designed to do.  

That said do we now want to add the additional information required to 
give the inexperienced like myself the ability to know what they must 
have for the base system and then what they need if they want to use 
OpenSSH - absolutely - but you can (and I am not saying you want to) 
accomplish the same thing with an FAQ.  In many cases simply displaying 
the Categories and dependencies where people could read them and select 
their packages based on them from within Setup might be enough although 
definitely not the way you would want to do it if you are trying to write 
a 'true package management tool.'.

I was only attempting to understand how either rpm or dpkg fit into the 
install or download operations in conjunction with setup.  I was only 
attempting to understand how setup essentially communicates with dpkg or 
rpm to accomplish the given task.  From what little I remember of rpm - 
it essentially accomplishes the task of a true package management tool 
without the use off setup.

<Getting off soapbox>

Thanks all for the additional information.