[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Cygwin Install, Misc. Documentation and Install Comments

From: Andrew <asha_at_onezero.org>
Date: 2003-01-10 00:34:00 CET

Hi, thanks to everyone that's responded so far.

sussman: thanks for the :) but I do not want to become a Subversion
developer. I'm not exactly freeloading here -- I've already contributed
something trying to get people to understand that it is a bit of a hassle
to use Subversion with Cygwin, and by writing up the documentation
comments (which nobody seems to have done anything with; I hope they
haven't fallen through the cracks). Building Subversion on Cygwin was
the first thing I tried. I do not have any more information about why
the build failed other than what I sent out in my first email.

Tim: using only relative path names doesn't seem to solve the problem
with "svn commit filename" where svn commit attempts to look at EDITOR,
which is most naturally expressed in a Cygwin path. I know I can get
around this particular problem by using "svn commit --F" or "svn commit
--message", but that's not what I was getting at. The main point is
that anyone trying to use Subversion with Cygwin is going to run into
things like this, that Cygwin+Subversion users will find it painful to
learn how to get around these hings, and if the developers of Subversion
want people to use it with Cygwin then they could work on this, or at
least acknowledge that there is some value in the feedback and that
they will think about it. I'd think that the Cygwin population would
harbor a pretty large number of potential Subversion users and that
it's attractive to the developers get Subversion running well on Cygwin,
regardless of how busy the developers are.


On Thu, Jan 09, 2003 at 04:53:52PM -0600, Leeuw van der, Tim wrote:
> Hi,
> I understand what you mean - however, I've been using it with only relative
> pathnames as arguments. Then you don't need the cygwin mount table. The
> current dir. for SVN will be the current dir for your bash shell.
> And my point was that the filenames that you enter into your bash shell (or
> whatever shell you use) will be understood by svn, even if they use the unix
> slash convention. So your filename-completion works, etc.
> I do agree that a cygwin-compilable svn would be nice, because then I could
> compile it myself ;-)
> Regards,
> --Tim
Received on Fri Jan 10 00:35:35 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.