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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <03b901c16d51$b8f75500$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" Cc: References: <3BE4D4A7 .2070900 AT ece DOT gatech DOT edu> <20011104104732 DOT X17306 AT cygbert DOT vinschen DOT de> <1004867892 DOT 5388 DOT 54 DOT camel AT lifelesswks> <3BE702C3 DOT 5010008 AT ece DOT gatech DOT edu> <1004999653 DOT 4685 DOT 20 DOT camel AT lifelesswks> <3BE71DF4 DOT 20802 AT ece DOT gatech DOT edu> <3BEFAA8F DOT 4020900 AT ece DOT gatech DOT edu> <3BF17502 DOT 6020902 AT ece DOT gatech DOT edu> <006101c16cd9$8c0e8770$0200a8c0 AT lifelesswks> <010e01c16cef$78c8be90$0200a8c0 AT lifelesswks> <3BF2CA1A DOT 34130B9D AT ece DOT gatech DOT edu> Subject: Re: patches to vendor source trees - discussion Date: Thu, 15 Nov 2001 08:17:09 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 14 Nov 2001 21:22:49.0210 (UTC) FILETIME=[82C9E5A0:01C16D52] ----- Original Message ----- From: "Charles Wilson" To: "Robert Collins" Cc: Sent: Thursday, November 15, 2001 6:46 AM Subject: Re: patches to vendor source trees - discussion > Robert Collins wrote: > > It's got what I was meaning in all those discussion. If you could put it > > up for comparison with your 1st and 2nd style tarballs that'd be great. > > Okay, it's up there. > > But it isn't a FULL example. You didn't modify the > CYGWIN-PATCHES/mktemp.README file to reflect *your* building style. You > didn't change CYGWIN-PATCHES/mktemp-1.3.1-1.sh to reflect the way *you* > think the build procedure should work. Both files still refer to things > like /usr/doc/cygwin/SOURCES and /usr/doc/cygwin/BUILD etc. Which is fine, because I've been keeping out of that part of the process. > You merely changed the name of the internal tarball slightly. Correct, because it should have been the vendors tarball as is. > I want to see a REAL, FULL example of your idea, as integrated with > setup's *current* capabilities. I *thought* that my -style2 did that. > You left my -style2 shell script as is, but changed just enough in the > package structure so that the script doesn't work. You changed a little > of the README but it still isn't a completely accurate representation of > *your* structure. I didn't realise I'd altered the README. Oops. I've been maintaining that what I'm talking about is orthogonal to the package building at this point. However I've updated the script & readme to use the structure I have in the tarball. I've also mailed you another style3 tarball... built via 'mktemp-1.3.1-1.sh all' > Also, if the -src tarball is going to contain mktemp-1.3.1-1.patch, then > the src tarball should be named mktemp-1.3.1-1-src.tar.bz2, NOT > mktemp-1.3.1-src.tar.bz2. Otherwise, how will you differentiate it from > the -src tarball that contains mktemp-1.3.1-2.patch? The outer tarball is named that isn't it? Or did I label it badly when I sent it to you. ... looks like I named it badly. Yes the -src tarball should be 1.3.1-1-src.tar.bz2 Rob