Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-Id: <4.3.1.2.20020427180026.02cbc078@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com Date: Sat, 27 Apr 2002 18:04:55 -0400 To: "Robert Collins" , "Charles Wilson" , "Gareth Pearce" From: "Larry Hall (RFK Partners, Inc)" Subject: RE: ITP: netpbm Cc: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 01:40 PM 4/27/2002, Robert Collins wrote: > > -----Original Message----- > > From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT edu] > > Sent: Sunday, April 28, 2002 2:46 AM > >... > > But cygwin is used on > > both NTFS and > > FAT... > >Which is the killer question: is adding a directory to the search path >more or less of a performance hog than adding x-100 .exes and/or .dll's >to the /usr/bin directory. And will the inevitable 'my dos script can't >find netpbm foobar tool' questions be worth it? No, not in my book. >Well my system32 directory here has 1971 files. Adding a coupla hundred >optional files doesn't seem all that bad to me. > >And hey, if FAT is too slow, folk can always install the windows ext2 >driver. Right, there are alternatives to this issue. I believe performance is an important concern but not to the exclusion of simple usability. Some people will complain if this package causes things to slow down for them. But everyone will complain if they can't run the package after they install it. I think we should absolutely avoid the latter case. The former we can deal with as required. Just my $.02. Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX