Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <000201c1014a$19cf53b0$6464648a@ca.boeing.com> From: "Michael A. Chase" To: Subject: Sample setup.ini Date: Sat, 30 Jun 2001 02:43:41 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 I think it would be very useful to get out a version of setup.exe that can recognize and ignore the new markers in setup.ini (). That way you could start including the markers in the production setup.ini before everyone switches over to a setup.exe that actually uses them. I am willing to provide an alternate branch to setup.exe if you are agreeable. I think it would be enough to start with the currently released version's source then add the changes to iniparse and inilex with the functions that process the new markers NOOPed. ======= I think "Basic" or "Essential" or "Required" would be a better name for the essential Cygwin packages than "Base". I think filutils should be in the "Base" category. People would be very surprised to find a system without cp, ls, mkdir, mv, and rm, The "requires:" marker might avoid that problem though. If so, several other packages should probably be in other categories in addition to "Base". ======= Additional category name suggestions: File Compression, Help, Backup, Image. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age.