Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Reply-To:	<nhv AT cape DOT com>
From:	"Norman Vine" <nhv AT cape DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: "shouted down", "shot down", apologies
Date:	Wed, 27 Jun 2001 17:34:03 -0400
Message-ID:	<00cb01c0ff50$e309a2e0$a300a8c0@nhv>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook 8.5, Build 4.71.2232.26
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4522.1200
In-Reply-To:	<03F4742D8225D21191EF00805FE62B9908E23ED9@aa-msg-01.medstat.com>
Importance:	Normal

John Wiersba writes:

> If csv is the only/best way, does someone have a cookbook which will 
>allow me to setup a test environment, 

The way I do this < and I am sure it is not the best but it works for me >
is to first create a directory to work in I'll call it $CYGWIN_SRC

place this shell script in that directory

======= cut here =======
#! /bin/sh
echo "(Logging in to anoncvs AT anoncvs DOT cygnus DOT com)"
echo "Checking out Cygwin"
echo "CVS password: anoncvs"
export CVSROOT=:pserver:anoncvs AT anoncvs DOT cygnus DOT com:/cvs/src
cvs login
cvs -z3 checkout winsup 2>&1 | tee cvs_co.log
./MakeCygwin.py
====== cut here =====

and place this python script in this same directory
http://home.cape.com/nhv/files/cygwin/MakeCygwin.py

>refresh the source, build everything, 

execute the above shell script and a tarball of the
Cygwin CVS files will be placed in this same directory
also under this directory you will have a ./usr directory 
containing the files in this tarball

>make a change, test it out, submit a patch -- 

I now just install this tarball by 
% cd /
% tar -xzvf PATH_TO_FRESH_TAR_BALL

then closing all applications using the Cygwin DLL
and copying the new cygwin1.dll from $CYGWIN_SRC / usr / bin / 
to $CYG_DRIVE / bin using a WIN32 tool < explorer, copy ect >

start using your new Cygwin

>all while keeping a working cygwin
>environment built off of setup.exe's download?

If for some reason I do not want to keep this version of Cygwin  
I either reinstall an earlier version that I have made using the same
techniques.  OR use the cygwin setup.exe program to reinstall
the latest official Cygwin distribution.

This method assumes that you have installed Python

FWIW
It normally takes less then 20 minutes for me to update and 
rebuild Cygwin using this method on a PIII 733 over a dialup.
It will take longer the first time in that CVS has to get all the
files initially.

I am sure there are better ways to do this
but until I discover them this works for me :-))

Comments and/or  Suggestions on how to do this solicited.

Cheers

Norman Vine


--
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/

- Raw text -