Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-Id: <5.1.0.14.0.20010703153653.02ddd7b0@mail> X-Sender: superbiskit AT mail X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 03 Jul 2001 15:41:31 -0400 To: bkeener AT thesoftwaresource DOT com, cygwin AT cygwin DOT com From: "David A. Cobb" Subject: Re: "shouted down", "shot down", apologies In-Reply-To: References: <20010627164651 DOT A24718 AT redhat DOT com> <03F4742D8225D21191EF00805FE62B9908E23ED9 AT aa-msg-01 DOT medstat DOT com> <20010627164651 DOT A24718 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed I know: This is a week old. I'm just playing catchup. At 6/27/01 05:39 PM (Wednesday), Brian Keener wrote: >I am probably going to jump into this now without intending to but this >really >does not answer his question - sorry Chris and I am not aiming this at you >Chris - This is simply an observation. He asked: > > >> So, if I want be able to rebuild all the cygwin packages, can I do > that from > >> source downloaded with setup.exe? Can someone recommend a convenient > way of > >> building a "test cygwin" from that source which can be switched to (via a > >> change to cygwin.bat) to try out changes? Or do I really have to go > the cvs > >> route and work with the latest/greatest bleeding-edge packages? If csv is > >> the only/best way, does someone have a cookbook which will allow me to > setup > >> a test environment, refresh the source, build everything, make a change, > >> test it out, submit a patch -- all while keeping a working cygwin > >> environment built off of setup.exe's download? > >As someone who is trying to learn C++ and never really worked with it much >and >as a contributor to the Cygwin project by contributing to setup.exe these are >questions that I and many others have asked before at various times. I have >read the above links before and probably missed where the answers to John's >questions were located but as far as I can tell there isn't a lot to get >someone going on contributing to Cygwin. Or let me say there is a not a >lot if >you are inexperienced in cvs, cygwin, C++, gcc, make as they are used in this >environment. I have essentially pieced together from various sources (you >Chris >and Earnie and Dj and whole lot of others) and reading the man pages and >asking >very pointed questions just enough to be able to make changes, compile and >test >them and then submit them. Having done all those things, pieced together the information, etc --- perhaps you would be so good as to write a wee bit of a document that could be referenced from the "Contributing" page? It might not be a "cookbook," but friendly tips are almost never unwelcome. David A. Cobb, Software Engineer, Public Access Advocate, All around nice guy. Get my PGP key at : Fingerprint=0x{6E3E_DB8C_2E8C_4248_62B2_FE29_08EE_CF0A_3629_E954} : "By God's Grace I am a Christian man, by my actions a great sinner." --The Way of a Pilgrim, R. M. French [tr.] Potentially Viral Software is any software for which you are not allowed to examine the source. Do not buy or use Potentially Viral Software! <---.----!----.----!----.----!----.----!----.----!----.----!----.----> -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/