From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26313 invoked by alias); 15 Jul 2002 15:02:48 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 26290 invoked from network); 15 Jul 2002 15:02:47 -0000 Received: from unknown (HELO ns.helixdigital.com) (68.15.28.22) by sources.redhat.com with SMTP; 15 Jul 2002 15:02:47 -0000 Received: from ns.helixdigital.com (alcocer@localhost [127.0.0.1]) by ns.helixdigital.com (8.12.2/8.12.2) with ESMTP id g6FF2lfs012568 for ; Mon, 15 Jul 2002 08:02:47 -0700 (PDT) Received: (from alcocer@localhost) by ns.helixdigital.com (8.12.2/8.12.2/Submit) id g6FF1Vus002031 for cygwin@cygwin.com; Mon, 15 Jul 2002 08:01:31 -0700 (PDT) Date: Mon, 15 Jul 2002 09:21:00 -0000 From: Dario Alcocer To: cygwin@cygwin.com Subject: Re: gzip.exe as symlink... Message-ID: <20020715080131.A27297@ns.helixdigital.com> References: <09b601c22bc1$ec09e870$2300a8c0@LAPTOP> <005601c22be1$c1fb8f00$0100a8c0@wdg.uk.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <005601c22be1$c1fb8f00$0100a8c0@wdg.uk.ibm.com>; from maxb@ukf.net on Mon, Jul 15, 2002 at 10:26:53AM +0100 X-SW-Source: 2002-07/txt/msg01161.txt.bz2 On Mon, Jul 15, 2002 at 10:26:53AM +0100, Max Bowsher wrote: > Never mind emacs - surely it makes more sense for gzip to be the real file, and > gunzip to be the symlink? Isn't that what most people would automatically > assume? Yes. I'd say that this qualifies as packaging bug. OTOH, I agree with Rob that the NTemacs package in question is probably broken also. -- Dario Alcocer -- Sr. Software Developer, Helix Digital Inc. alcocer@helixdigital.com -- http://www.helixdigital.com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/