delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2003/07/16/07:53:04

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 16 Jul 2003 19:06:11 +1000 (EST)
From: luke DOT kendall AT cisra DOT canon DOT com DOT au
Subject: Re: Ideas re problem reporting
To: cygwin AT cygwin DOT com
In-Reply-To: <1058333460.3403.303.camel@localhost>
MIME-Version: 1.0
Message-Id: <20030716090612.1AE0834381@nevin.research.canon.com.au>

On 16 Jul, Robert Collins wrote:
>  However, a registry entry won't correct this: only the user knows 
>  exactly what tool they used, unless we go down some insane DRM style 
>  path - and I won't be taking setup down that path. 

You mean, even if setup just recorded whether it had just completed a
full, or a default, or some intermediate install - there would be
nothing to stop a naughty user from faking the same entry manually?

luke 


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


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019