From: Jens Schweikhardt <schweikh@schweikhardt.net>
To: cygwin@cygwin.com
Subject: How is setup.ini generated these days?
Date: Sun, 17 Apr 2011 04:10:00 -0000 [thread overview]
Message-ID: <20110416190115.GB11826@schweikhardt.net> (raw)
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
next reply other threads:[~2011-04-16 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 4:10 Jens Schweikhardt [this message]
2011-04-17 17:35 ` Yaakov (Cygwin/X)
2011-04-17 17:36 ` Jens Schweikhardt
2011-04-17 21:19 ` Christopher Faylor
2011-04-18 23:37 ` Jens Schweikhardt
2017-02-03 3:29 ` Steven Penny
2017-02-03 4:12 ` Steven Penny
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110416190115.GB11826@schweikhardt.net \
--to=schweikh@schweikhardt.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).