This is the mail archive of the
cygwin
mailing list for the Cygwin project.
How is setup.ini generated these days?
- From: Jens Schweikhardt <schweikh at schweikhardt dot net>
- To: cygwin at cygwin dot com
- Date: Sat, 16 Apr 2011 21:01:15 +0200
- Subject: How is setup.ini generated these days?
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