Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <013c01c19af8$a8f46380$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Michael Adler" <adler@glimpser.org>, <cygwin@cygwin.com>
References: <Pine.NEB.4.43.0201111322560.22895-100000@reva.sixgirls.org>
Subject: Re: setup.ini for custom distrobution
Date: Sat, 12 Jan 2002 10:35:31 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

----- Original Message -----
From: "Michael Adler" <adler@glimpser.org>


> How can I write a setup.ini so that it will install everything without
> having to click on 40 packages?

1) Don't use a setup.ini.
2) Put everything into base.
3) read http://www.cygwin.com/setup.html

> If this is a RTFM situation, please show me the Fine Manual.

No, it's a case of read the manual we wish we had time to write. The
cygwin-apps archives include the discussion on setup development, which
would answer this for you.

> If it goes well, I might write a doc 'how to create your own cygwin
> distro'.

Right now, with the number of contributors we've got, this could be
disastrous :}.

Also, you don't _need_ a custom distribution with the next release of
setup. You can just merge in a 2nd setup.ini that causes the changes you
want, and adds any needed packages.

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/