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:	Sun, 4 Nov 2001 10:47:32 +0100
From:	Corinna Vinschen <cygwin-apps AT cygwin DOT com>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: patches to vendor source trees - discussion
Message-ID:	<20011104104732.X17306@cygbert.vinschen.de>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
References:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF7A48 AT itdomain002 DOT itdomain DOT net DOT au> <3BE4D4A7 DOT 2070900 AT ece DOT gatech DOT edu>
Mime-Version:	1.0
User-Agent:	Mutt/1.2.5i
In-Reply-To:	<3BE4D4A7.2070900@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sun, Nov 04, 2001 at 12:39:51AM -0500

On Sun, Nov 04, 2001 at 12:39:51AM -0500, Charles Wilson wrote:
> Robert Collins wrote
> 
> >>You've stated several times that you're looking only at "baby 
> >>steps" -- but 
> >>I think baby steps are counterproductive here.  Imagine a 
> >>
> > 
> > I agree in principle. The issues I percieve is that
> > 1) setup.exe isn't ready for more than bare bones changes - regardless
> > of rpm or dpkg inspiration.

Guys,

I would prefer to keep it simple.  And since we already have seen
implementations of rpm for Cygwin (regardless of the "replace
DLL/EXE while running" problem) I would propose the rpm way which
would easily fit in our current packaging scheme.

- setup.exe creates the /usr/src/cygwin directory and it's subdirs
  BUILD, RPMS, SOURCES, SPECS and SRPMS.

- Our current tar.bz2/tar.gz source packages are copied on demand into
  /usr/src/cygwin/SOURCES.  They will not extracted in future.

- New packages or new versions of existing packages could choose to
  repack as genuine .tar.[bg]z* file (using the already existing naming
  convention plus a patch file which is
  called package-<version>-<cygwin subversion>.dif

- If a package maintainer likes, he can choose to add a 
  package-<version>-<cygwin subversion>.spec file to the directory
  which then will be copied to /usr/src/cygwin/SPECS.

That's all.  And that's everything which should be done by setup, IMO.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

- Raw text -