This is the mail archive of the
mailing list for the Cygwin project.
Collection of new/updated packages available for testing (rpm)
- To: cygwin-apps at sources dot redhat dot com
- Subject: Collection of new/updated packages available for testing (rpm)
- From: David Starks-Browning <starksb at ebi dot ac dot uk>
- Date: Tue, 22 Aug 2000 10:21:54 +0100
- References: <E3547IPM2AUAP*@MHS>
On 22 Aug 00, "Michael Ring" <Michael.Ring@t-mobil.de> (Tel +49 228/936-2621) writes:
> Here's why I did it:
> o rpm offers far more flexibility to package installation / deinstallation than
> classical tar.gz files.
> o Things like postinstall and preremove-scripts can easily be included in a
> software package.
> o Sources live in a special file called the source-rpm. The original sourcecode
> of a software, patches to make it work and something like a script to build the
> software (called spec-file) is also included.
> o The binary distribution of a software package lives in rpm-files. Included in
> this simgle file are the binaries, custom postinstall or preremove scripts and
> dependency information (What does a package need to run, what does it provide to
> 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.