Message-Id: <200005011605.MAA21829@delorie.com>
Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
From: "Parker, Ron" <rdparker AT butlermfg DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: RE: Time for a new DLL release
Date: Mon, 1 May 2000 12:06:18 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="windows-1252"

> From: Corinna Vinschen [mailto:corinna AT vinschen DOT de]

> Do you think that each package which is installed as a part of
> the local cygwin install should have it's own entry in the windows
> "Add/Remove Programs" tab? Just a question. It would completely
> replace the standard rpm database then, isn't it? Nevertheless
> rpm itself has to be a cygwin app, IMO, because I would like
> to be able to use it on the command line.

I agree that rpm needs to be a cygwin application.  I did not mean to imply
that it would be a non-cygwin Windows native application. 

I have mixed thought on having one entry in the "Add/Remove Programs" tab
for each package.  In a large installation, this could result in a very long
list of packages.  I realize cygwin isn't Linux.  But in Linux there can be
hundreds of packages installed on a system.  On the otherhand it would work
out well for smaller installations.  

If we decided to go with a single entry like "Cygwin Programs" I would
recommend launching the UI and allowing the user to install, remove, or
update packages from there.  On the otherhand if we went with an entry per
package, the easiest solution would be to ask rpm to uninstall the package
and allow it to fail if there are other packages installed that depend upon
it.