Mail Archives: cygwin-apps/2000/08/22/06:20:29
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).
Note: You have to bootstrap your environment to the point you can _use_ rpm
style tools. DJ's setup.exe is essential to do that, but the possibility
exists to only distribute enough binary files in .tar.gz format to run rpm,
and distribute everything beyond that as rpm. then setup.exe can untar those
core files, and call rpm to do the rest. AFAIK that is what the redhat linux
installer does - bootstraps without rpm, and then runs rpm for
__everything__ else.
Rob
----- Original Message -----
From: "David Starks-Browning" <starksb AT ebi DOT ac DOT uk>
To: <cygwin-apps AT sources DOT redhat DOT com>
Sent: Tuesday, August 22, 2000 7:21 PM
Subject: Collection of new/updated packages available for testing (rpm)
.....
> > All those facs faciliate the process of maintaining software. This makes
rpm the
> > choice of many linux-dists like redhat, mandrake, suse and others.
>
> How is this useful to Cygwin? Is it better than, say, DJ's setup.exe?
>
> I've never used rpm myself, so I'm probably just ignorant of its magic.
>
> Regards,
> David
>
>
- Raw text -