Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Fri, 23 May 2003 01:07:17 +0900 (JST)
Message-Id: <20030523.010717.42254089.gotoh@taiyo.co.jp>
To: cygwin@cygwin.com
Subject: Re: CVS through a proxy
From: Shun-ichi GOTO <gotoh@taiyo.co.jp>
In-Reply-To: <Pine.GSO.4.44.0305221034340.7611-100000@slinky.cs.nyu.edu>
References: <20030522.153540.99612744.gotoh@taiyo.co.jp>
	<Pine.GSO.4.44.0305221034340.7611-100000@slinky.cs.nyu.edu>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


>>>>> at Thu, 22 May 2003 10:37:49 -0400 (EDT),
>>>>> Igor Pechtchanski <pechtcha@cs.nyu.edu> said,

> I saw on your site that 'connect' compiles on Cygwin.  Did you consider
> offering it as a Cygwin package, so that people can install it from the
> mirrors?

Because I don't know how many user using it, I defered considering such
a contribution. Sorry. There's no problem making package but I didn't
know how to.  What should I do?


> Also FYI, Cygwin's CVS is still on 1.11.0 (1.11.5 has just been announced
> as a test release).  Chuck (the CVS maintainer) might consider patching
> CVS to have proxy functionality, so maybe you could coordinate.  Chuck?

Oh, I didn't follow such a topic 'cause I'm very busy for some months.
# and stil now :-(

Proxying is FAQ for Windows users, I think. I made 'tsocks.c' as tiny
library file without depending specific application program.  Actually
I'm using it with cvs, rsync and subversion.  But it is made only for
satisfying my use. So it is not enough functionality and not
sophisticated way. If you think it is usefull, I'll contribute it and
help as possible.

P.S.
I'm using cvs since about 1.10 until now built with standard way like:

  $ sh ./configure && make

Now I have no major problem with this binary on my use.
So I don't recognize what matter should be considered for cygwin porting.

--- Regards,
 Shun-ichi Goto  <gotoh@taiyo.co.jp>
   R&D Group, TAIYO Corp., Tokyo, JAPAN

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

