Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Ralf Habacker" <Ralf.Habacker@freenet.de>
To: "Charles Wilson" <cwilson@ece.gatech.edu>
Cc: "cygwin" <cygwin@cygwin.com>
Subject: RE: rpm-4.1 successful compile on Cygwin
Date: Sat, 8 Mar 2003 10:02:55 +0100
Message-ID: <003d01c2e551$81c02480$0a1c440a@BRAMSCHE>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <3E68FD91.7030608@ece.gatech.edu>

Max Bowsher wrote:
>
> > I'm not quite sure rpm really is desirable for the Cygwin dist, unless it
> > was decided to transition to rpm packages exclusively once setup was
> > suitably adapted.
>
> Well, there are grand designs eventually to generalize setup so that it
> can accept tar.bz2 (or .cyg?) packages, as well as linking to (a windows
> native version of...) librpm and libdeb to provide rpm and deb support.
>   There are, of course, MAJOR difficulties with this, which have yet to
> be addressed (like keeping the setup installed.db, rpm's db, and deb's
> "db" all in sync.  Bringing setup's native dependency-resolution logic
> up to the level provided by deb and to a lesser extent rpm.
> Commandline/scripting support. etc etc)
>
> But, rpm has been around for years on cygwin without the sky falling.  I
>   used it back when I provided perl-for-cygwin, as a means of keeping
> track of binary dists of perl modules.  I'm sure there are other,
> similiarly limited uses that won't cause armageddon.

yes, an example are the original kde3 i18n rpm language packages which are
directly usable for kde3/cygwin. Using this rpm packages avoids the needs for
repackaging of about 50 packages.

Ralf


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/