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: Fri, 2 Nov 2001 21:25:58 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Re: patches to vendor source trees - discussion
Message-ID: <20011102212558.F31918@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
References: <1004752145 DOT 521 DOT 38 DOT camel AT lifelesswks> <20011102210311 DOT D31918 AT redhat DOT com> <1004753755 DOT 520 DOT 55 DOT camel AT lifelesswks>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1004753755.520.55.camel@lifelesswks>
User-Agent: Mutt/1.3.21i

On Sat, Nov 03, 2001 at 01:15:54PM +1100, Robert Collins wrote:
>On Sat, 2001-11-03 at 13:03, Christopher Faylor wrote:
>>Couldn't the patch remove itself?
>
>Not if you create the patch via diff!

Why?  The patch could patch itself into a zero length file and the file
could be removed via "patch -E".

>> One problem, of course, is that patch can't reliably remove a file.  It
>> can remove files that become empty but, AFAIK, it can't remove directories
>> that are made obsolete by the patch.
>
>So maybe we should provide unpatched directories, and a patch to make it
>cygwin-ready?

That's the way a lot packages do it.  I wouldn't mind that at all, if I
thought that our audience could handle it.

>> How does debian handle this?  Is it similar to the method that you
>> outlined?
>
>Funnily enough, when you download the source via apt you get 3 files and
>a dir:
>
>package-version.orig.tar.gz
>package-version-suffix.diff.gz
>package-version-suffix.dsc
>
>package-version is the vendor source tree unaltered. (and has no suffix)
>the diff.gz makes the vendor tree debian package creation tools ready
>the .dsc file is a PGP signed control file that includes all the
>metadata - maintainer, architecture, build-dependencies, source and diff
>file crc's etc. (The signing is to guarantee the file crc's).
>
>And there is a tool that will download those three files via apt-get ,
>and then extract, patch and build a package for one, in one command.
>Quite nice really.

Yes, it is.  Lets do that!  If we have a tool that will manage this, I
think this is a win.

cgf