Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Michael Ring To: Jan Nieuwenhuizen Cc: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: rpm-based installation of cygwin-485-snapshot Date: Tue, 28 Mar 2000 00:30:04 +0200 Message-ID: References: <200003272223 DOT AAA25881 AT appel DOT dyndns DOT org> In-Reply-To: <200003272223.AAA25881@appel.dyndns.org> X-Mailer: Forte Agent 1.6/32.525 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id RAA13568 On Tue, 28 Mar 2000 00:23:08 +0200, you wrote: > >> Hi! >> >> I would like to propose an alternative (or additional) installation >> method for upcomming cygwin-releases. > > >Wow, I really wish Cygnus will go the rpm way (at least until dpkg has >been fixed/rewritten). Me, too 8-) > >When I had to use Windows, I made an ugly port of rpm to make upgrading >of our internal user packages managable, as well as packaging simple >and uniform across GNU/Linux, GNU/Windows. > >How much effort was involved in porting rpm? I'm very much interested >in your patches/reworked .spec files. > I spent quite a while on fixes & testing them. I am sure I have not fixed all issues and have also used some dirty hacks (I am more a pascal/python/sh fan than a c-programmer ;-) ) but rpm works fine for me now which means that building, packaging and installation with dependency-checking works. I will send the patches for rpm-3.0.4 to you in another mail in order not to waste bandwith in this list here. I will also make the spec files available for download as soon as I have finished my cleanup-activities. >Just two weeks ago, I've setup a cross-development environment to >provide binaries for our Windows users; and again experienced the >pain of missing a package manager that Cygnus people would use. >So, I found myself writing a silly script to compile and setup the >cross-development tools, and do the `untar, patch, configure, make, >install, zip' sequence. > >Greetings, > >Jan. Till soon, Michael