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: Packaging software built with cygwin
From: Robert Collins <rbcollins AT cygwin DOT com>
To: Jay Maynard <jmaynard AT conmicro DOT cx>
Cc: cygwin AT cygwin DOT com
In-Reply-To: <20030205125545.A10690@thebrain.conmicro.cx>
References: <20030204194653 DOT A5738 AT thebrain DOT conmicro DOT cx>
	 <Pine DOT GSO DOT 4 DOT 44 DOT 0302042115170 DOT 24195-100000 AT slinky DOT cs DOT nyu DOT edu>
	 <20030204204803 DOT A6191 AT thebrain DOT conmicro DOT cx>
	 <20030205033246 DOT GA4959 AT redhat DOT com>
	 <20030205111822 DOT B9661 AT thebrain DOT conmicro DOT cx>
	 <20030205175543 DOT GB17331 AT redhat DOT com>
	 <20030205125545 DOT A10690 AT thebrain DOT conmicro DOT cx>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-6znL8N7aNy0lc+cscr4j"
Organization: 
Message-Id: <1044481249.18388.81.camel@localhost>
Mime-Version: 1.0
Date: 06 Feb 2003 08:40:49 +1100

--=-6znL8N7aNy0lc+cscr4j
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Thu, 2003-02-06 at 05:55, Jay Maynard wrote:


> > A setup.ini with just the cygwin DLL in it seems pretty simple.
>=20
> True. OTOH, when setup.exe changes, the format of that file is subject to
> change (see Igor's warning in the message where he first suggested that).=
 I
> can insulate myself from that by distributing setup.exe, but then I'm bac=
k
> in the same boat of making sure that I distribute the source code that's
> used to generate it.

We're in that boat too. (I'm the setup.exe maintainer). And we don't
break compatability at any significant speed - we *alway* deprecate for
at least one release, to allow third party sites (ones with their own
custom setup.ini) to catch up in their own time.

For instance, uncompressed setup.ini's are still supported, as a
fallback when .bz2 compressed ones are not found.

As far as distributing multiple versions of setup.exe's source, it's
easy: only distribute the current version. You don't need to distribute
old versions, because you can just update your setup.ini.


> > Supporting other people's distributions is not a core focus of
> > setup.exe.  However, if this is important to you it should be pretty
> > easy for you to submit patches to do what you want.
>=20
> I'll take a look in my copious free time.

Do that. There is very little that would need doing, if I intuit your
needs correctly.

Rob
--=20
GPG key available at: <http://users.bigpond.net.au/robertc/keys.txt>.

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

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

iD8DBQA+QYTgI5+kQ8LJcoIRAi6sAJ4x8oNwyaiY8aea4YbSzGNNk7eBsQCgmr+z
KBnGE7tL7h4QVOHZlnJNsvM=
=e+fF
-----END PGP SIGNATURE-----

--=-6znL8N7aNy0lc+cscr4j--