Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
Date:	Fri, 5 Oct 2001 10:16:23 -0400
From:	Jason Tishler <jason AT tishler DOT net>
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: setup.ini, setup.hint, and update-setup
Message-ID:	<20011005101623.N1544@dothill.com>
Mail-Followup-To:	cygwin-apps AT cygwin DOT com
Mime-Version:	1.0
In-Reply-To:	<20011002173634.A4473@redhat.com>
User-Agent:	Mutt/1.3.18i

Chris,

[Sorry, for chiming in late, but I have been on vacation for the last 5
days.]

On Tue, Oct 02, 2001 at 05:36:34PM -0400, Christopher Faylor wrote:
> I'm not going to guarantee that update-setup is around for the long haul.
> That's one reason why it is not publicly available.

I have found it very useful to be able to generate "private" setup.ini
files via update-setup.  For example:

    update-setup /misc/cygwin jt

splices a "jt" branch onto my local Cygwin mirror.

Do you envision any way to accomplish this, when (and if) update-setup
meets its demise?  Note that I'm quite willing to do the work -- I'm just
trying to make sure that the necessary hooks are in place in whatever
will be generating setup.ini going forward.

Thanks,
Jason

- Raw text -