X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
Subject:	Re: Feature Request: bzr package only works within cygwin
From:	Phillip Lord <phillip DOT lord AT newcastle DOT ac DOT uk>
Date:	Thu, 11 Sep 2008 17:23:54 +0100
Message-ID:	<EMEW-k8AHNsff4c5d438f298fdec8b6545d96addcf7-87k5ditzvp.fsf@dinley.ncl.ac.uk>
User-Agent:	Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
MIME-Version:	1.0
X-smtpf-Report:	client=relay,white,ipv6; mail=; rcpt=white
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

  >> And not with any non-cygwin program. bzr is in python, rather than an
  >> executable/binary file. The combination of native Emacs and cygwin is
  >> very common.

  cgf> I sure love bold assertions with no supporting facts.

  cgf> Here's my counter to that: No it isn't.

Have it which ever way you want. 



  >> >> Would it be possible to get this added to the cygwin package?
  >> 
  cgf> No. We don't add .bat files to Cygwin.
  >> 
  >> Yes you do. Cygwin.bat. startxwin.bat, several in python.

  cgf> Ok. Let me amend the unequivocal statement.

  cgf> The cygwin .bat file is an entry to the cygwin environment. It is a
  cgf> compromise. Ditto the .bat in X.

  cgf> Other packages may already include .bat files which are already part of
  cgf> the distribution or the maintainer may have misguidedly felt that it
  cgf> was a good idea to include a .bat file.

  cgf> It is a slippery slope to start adding a .bat file for every script in
  cgf> the distribution. Carried to its logical conclusion, we'd end up with a
  cgf> lot of .bat files and mailing list traffic from people who were
  cgf> "tweaking" the .bat files or asking questions about .bat syntax. That
  cgf> is about as far from the purpose of this project as you can get.

One .bat file to rule them all. They would all be exactly the same. 


  >> My use case seems perfectly reasonable;

  cgf> That may be but your use case is not aligned with the project goals.

Yes, that would have been a perfectly good response. 

  >> having bzr work from outside the bash shell seems a reasonable to wish
  >> for. If you don't like my solution, can you suggest an alternative?

  cgf> Use Cygwin version of tools and you'll be all set. Alternatively use
  cgf> native versions of tools and you won't use Cygwin.

  cgf> Or, just create your own .bat file and do whatever you like.

Actually, what I like is that when I spend time and effort writing up a
perfectly reasonable RFE, with a perfectly reasonable use case and a perfectly
reasonable prospective solution, I get treated with politeness and respect.

You have shown that you can give a perfectly reasonable explanation as to the
position -- whether I agree with it or not. You could have done that in your
original reply with little more effort than your blank "No" answer.

Thanks for your time

Phil


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

- Raw text -