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: <3BF5FAF4.7090709@ece.gatech.edu> Date: Sat, 17 Nov 2001 00:51:48 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: Gareth Pearce CC: cygwin-apps AT cygwin DOT com Subject: Re: patches to vendor source trees - discussion 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> <03b901c16d51$b8f75500$0200a8c0 AT lifelesswks> <3BF2FE81 DOT C586876A AT ece DOT gatech DOT edu> <001501c16d6f$a9899c90$0200a8c0 AT lifelesswks> <3BF3180C DOT 8A99A5E8 AT ece DOT gatech DOT edu> <3BF5EEC6 DOT 4020803 AT ece DOT gatech DOT edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Gareth Pearce wrote: > As a not a maintainer quite yet - Might put my comment forth anyway... > > I am closer to favouring 1 then 3 ... and not 2 ... > but neither is how I would naturally think of things... - thats assuming > that the package is called cygwin that is being talked about in #1 > #4 - which is like #1 other then difference stated. Nope. cygwin/ is a standin for redhat/ Like, srpm's get installed into /usr/src/redhat/SOURCES/ on Red Hat Linux (regardless of what package -- libpng, ssh, whatever -- we're talking about). They ALL go in /usr/src/redhat/SOURCES/ On Mandrake, that's /usr/src/rpm/SOURCES/ So, we're cygwin: /usr/src/cygwin/SOURCES/ > -src tarball contains > cygwin/ > cygwin/ > (possibly other stuff in cygwin/, if necessary - post install > scripts come to mind) > cygwin/ > newly generated bin tarballs placed in cygwin/BUILT > newly generated src tarballs placed in cygwin/BUILT > > The process of building would probably require the construction of some > other directories, build scripts choice and also its perogative to clean > them up - and yes its sort of sounding rather makefileish ... that way you > can just patch ths source only ... or patch and compile ... or patch compile > package-bin ... or patch compile install[-strip] and finally clean > Not sure what the point of generating src tarballs is... but I left that > there... > > I personally think that 3 files in one directory isnt getting too crowded... > and that all the extra directorys seem like overkill. > Then again - I also dont care about things looking like RPM or pkg > formats... Most of these comments ^^^ seem to be based on the misconception that there would be oodles of SOURCES, BUILD etc directories -- one for each unpacked -src. Not so. Like this: /usr/src/cygwin/SOURCES/tiff-ver.tar.bz2 (pristine) /usr/src/cygwin/SOURCES/ssh-ver.tar.bz2 (pristine) /usr/src/cygwin/SOURCES/tiff-ver-rel.patch /usr/src/cygwin/SOURCES/ssh-ver-rel.patch /usr/src/cygwin/SPECS/tiff-ver-rel.sh /usr/src/cygwin/SPECS/ssh-ver-rel.sh NOT /usr/src/tiff/SOURCES/tiff-ver.tar.bz2 (pristine) /usr/src/tiff/SOURCES/tiff-ver-rel.patch /usr/src/tiff/SPECS/tiff-ver-rel.sh /usr/src/ssh/SOURCES/ssh-ver.tar.bz2 (pristine) /usr/src/ssh/SOURCES/ssh-ver-rel.patch /usr/src/ssh/SPECS/ssh-ver-rel.sh > > > if I appear to have no clue ... thats understandable ;) > Anyway about it I can see that I am actually going to have to write proper > patches - rather then just keeping a copy of hacked files :P - all for the > best though... Hopefully, once "we" reach a decision, there will be some nice example scripts for handy patch creation, -src packaging, etc. (Take a good look at the .sh files at the URL posted earlier). Just modify to suit. --Chuck