Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com X-Injected-Via-Gmane: http://gmane.org/ To: cygwin@cygwin.com From: Steven Elliot Harris Subject: Re: Third-party products that include cygwin Date: Sat, 13 Dec 2003 11:49:15 -0800 Organization: SEH Labs Lines: 22 Message-ID: <833cbosdl0.fsf@torus.sehlabs.com> References: <3D848382FB72E249812901444C6BDB1D022F46DE@exchange.timesys.com> <20031212224538.GB4582@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Rational FORTRAN, cygwin32) Cancel-Lock: sha1:El0968/cjXL8c6n7wDS+N0kisvw= Christopher Faylor writes: > I think this is how the BitKeeper folks do it, too, FWIW. For the record, I'm pretty sure they've recently decided to stop doing this, per this message¹ from Larry McVoy. Note the third paragraph regarding "future directions." It sounds like they'll play nice alongside Cygwin, but not be built on top of it. The last time I tried to install BitKeeper (around October 2003), it trashed my Cygwin mounts even though I told the installer not to touch my Cygwin setup, and even then BitKeeper wouldn't run without crashing. Apparently it wasn't (re)built to handle Cygwin 1.5.x. Sadly, as a result, I've been without BitKeeper on my new computer. Footnotes: ¹ http://www.bitmover.com/pipermail/bitkeeper-users/2003-October/001025.html -- Steven E. Harris -- 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/