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: Tue, 22 Aug 2000 11:40:31 +0100
Message-ID: <260-Tue22Aug2000114031+0100-starksb@ebi.ac.uk>
X-Mailer: emacs 20.6.1 (via feedmail 9-beta-7 I);
	VM 6.75 under Emacs 20.6.1
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: cygwin-apps AT sources DOT redhat DOT com
Subject: Re: Collection of new/updated packages available for testing (rpm)
In-Reply-To: <004901c00c23$a57c7680$f7c723cb@lifelesswks>
References: <E3547IPM2AUAP*@MHS>
	<5473-Tue22Aug2000102154+0100-starksb AT ebi DOT ac DOT uk>
	<004901c00c23$a57c7680$f7c723cb AT lifelesswks>

On Tuesday 22 Aug 00, Robert Collins writes:
> As I see it rpms (or the debian equivalent) offer three key improvements
> over DJ's setup.exe and any similar tar based solution:
> * pre-post install/uninstall scripts (i.e. check if you have /etc/services,
> if not install it, if you do call sed and edit it rather than replacing
> it...)
> * dependancy tracking. Each RPM
> * uninstall functionality (the database knows what was installed, what
> uninstalling it will break, what to do to uninstall item x).

Interesting.  Would dependency tracking know that 'make' requires
'ash', for example?

Isn't it a big job for the package maintainers to get all the scripts
& dependencies right?  (Or are there automated tools for that?)

Thanks,
David