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
Subject:	Re: Ideas re problem reporting
From:	Robert Collins <rbcollins AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
In-Reply-To:	<20030716033302.GA6050@redhat.com>
References:	<o5bpcv867rhlo17vfmclotlv5nkr9f9m8f AT 4ax DOT com>
	<20030716002142 DOT E1F2434381 AT nevin DOT research DOT canon DOT com DOT au>
	<20030716033302 DOT GA6050 AT redhat DOT com>
Message-Id:	<1058333460.3403.303.camel@localhost>
Mime-Version:	1.0
Date:	16 Jul 2003 15:31:00 +1000

--=-FSd7GvLBjBnE9rxArtRh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Wed, 2003-07-16 at 13:33, Christopher Faylor wrote:

> cygcheck -rsv (or cygcheck -c) already implies this.  If the output
> from cycheck doesn't include package information, then the packages
> weren't installed via setup.exe.

I've seen at least one script that (badly) reverse engineered setup's db
files and attempts to create compatible ones.

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.

Rob
--=20
GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.

--=-FSd7GvLBjBnE9rxArtRh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/FOMTI5+kQ8LJcoIRAmdAAJ9TRSFBcXbj4UYm7Uj6psgMUxBOHQCfQ0vv
cmMpOIwQDHqg5CI9dtw+2EE=
=UvtU
-----END PGP SIGNATURE-----

--=-FSd7GvLBjBnE9rxArtRh--

- Raw text -