Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <070f01c19fda$d81f4760$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" , "Joshua Franklin" Cc: References: <20020117190003 DOT 69826 DOT qmail AT web20009 DOT mail DOT yahoo DOT com> <3C473531 DOT 7020905 AT ece DOT gatech DOT 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 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 18 Jan 2002 04:46:42.0087 (UTC) FILETIME=[1FA86B70:01C19FDB] ----- Original Message ----- From: "Charles Wilson" > 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/