Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <070f01c19fda$d81f4760$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Charles Wilson" <cwilson@ece.gatech.edu>,
   "Joshua Franklin" <joshuadfranklin@yahoo.com>
Cc: <cygwin@cygwin.com>
References: <20020117190003.69826.qmail@web20009.mail.yahoo.com> <3C473531.7020905@ece.gatech.edu>
Subject: Re: "RTFM'ing": readily accessible user documentation?
Date: Fri, 18 Jan 2002 15:44:41 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Charles Wilson" <cwilson@ece.gatech.edu>
> Should setup.exe *refuse* to install a file called "/usr/info/dir" --
> just to keep us safe?  Or is that setting a bad precedent?  [Or maybe
> upset can "lint" the packages on sourceware, and refuse to add
> foo-1.2.tar.gz to setup.ini if it contains a proscribed file like
> /usr/info/dir]

On my personal TODO list is a command line unix package linter.
Setup.exe may some mechanism to manage state data - /etc/foo.cfg,
/usr/info/dir etc, but I think a simpl solution to catch 99% of cases is
the package linter. And yes, it should refuse to add the package, and
email the maintainer (IMO).

Rob


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