X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.2 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Date: Sat, 16 Apr 2011 21:01:15 +0200 From: Jens Schweikhardt To: cygwin AT cygwin DOT com Subject: How is setup.ini generated these days? Message-ID: <20110416190115.GB11826@schweikhardt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com hello, world\n I'm trying to make a package server as described on http://sourceware.org/cygwin-apps/package-server.html I've rsynced the complete "release" tree (skipping *-legacy). However, running genini release/* > setup.ini with genini 1.13 from http://cygwin.com/cgi-bin/cvsweb.cgi/genini/?cvsroot=cygwin-apps) produces a lot of errors and warnings and the resulting setup.ini is much smaller than the official one that comes with rsyncing (300k vs 1300k). So the question is: how is the official setup.ini created from a release directory? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple