* How is setup.ini generated these days?
@ 2011-04-17 4:10 Jens Schweikhardt
2011-04-17 17:35 ` Yaakov (Cygwin/X)
0 siblings, 1 reply; 7+ messages in thread
From: Jens Schweikhardt @ 2011-04-17 4:10 UTC (permalink / raw)
To: cygwin
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: How is setup.ini generated these days?
2011-04-17 4:10 How is setup.ini generated these days? Jens Schweikhardt
@ 2011-04-17 17:35 ` Yaakov (Cygwin/X)
2011-04-17 17:36 ` Jens Schweikhardt
0 siblings, 1 reply; 7+ messages in thread
From: Yaakov (Cygwin/X) @ 2011-04-17 17:35 UTC (permalink / raw)
To: cygwin
On Sat, 2011-04-16 at 21:01 +0200, Jens Schweikhardt wrote:
> 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).
Many packages are in subdirectories of release. Try this instead:
genini --output=setup.ini `find release/ -name setup.hint | sed 's|/setup\.hint$||g'`
Yaakov
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: How is setup.ini generated these days?
2011-04-17 17:35 ` Yaakov (Cygwin/X)
@ 2011-04-17 17:36 ` Jens Schweikhardt
2011-04-17 21:19 ` Christopher Faylor
0 siblings, 1 reply; 7+ messages in thread
From: Jens Schweikhardt @ 2011-04-17 17:36 UTC (permalink / raw)
To: cygwin
On Sat, Apr 16, 2011 at 11:20:47PM -0500, Yaakov (Cygwin/X) wrote:
# On Sat, 2011-04-16 at 21:01 +0200, Jens Schweikhardt wrote:
# > 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).
#
# Many packages are in subdirectories of release. Try this instead:
#
# genini --output=setup.ini `find release/ -name setup.hint | sed 's|/setup\.hint$||g'`
Thanks, and I also found the --recursive option. Now I'm running this:
genini --output=setup.ini --recursive --okmissing=source release
This gets close to 1300k but not quite. There are small differences that
apparently result from some sort of postprocessing, such as:
* If a package has no "requires" tag, it gets one with "cygwin"
* If a "requires:" tag does not include "cygwin" it gets one
Apart from that many "source", "install" and "version" tags are different.
What is the script that the official setup.ini is generated with?
Is this list the right place to ask this? If not, where should I ask?
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: How is setup.ini generated these days?
2011-04-17 17:36 ` Jens Schweikhardt
@ 2011-04-17 21:19 ` Christopher Faylor
2011-04-18 23:37 ` Jens Schweikhardt
0 siblings, 1 reply; 7+ messages in thread
From: Christopher Faylor @ 2011-04-17 21:19 UTC (permalink / raw)
To: cygwin
On Sun, Apr 17, 2011 at 02:28:00PM +0200, Jens Schweikhardt wrote:
>On Sat, Apr 16, 2011 at 11:20:47PM -0500, Yaakov (Cygwin/X) wrote:
># On Sat, 2011-04-16 at 21:01 +0200, Jens Schweikhardt wrote:
># > 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).
>#
># Many packages are in subdirectories of release. Try this instead:
>#
># genini --output=setup.ini `find release/ -name setup.hint | sed 's|/setup\.hint$||g'`
>
>Thanks, and I also found the --recursive option. Now I'm running this:
>
> genini --output=setup.ini --recursive --okmissing=source release
>
>This gets close to 1300k but not quite. There are small differences that
>apparently result from some sort of postprocessing, such as:
>
> * If a package has no "requires" tag, it gets one with "cygwin"
> * If a "requires:" tag does not include "cygwin" it gets one
>
>Apart from that many "source", "install" and "version" tags are different.
>
>What is the script that the official setup.ini is generated with?
>Is this list the right place to ask this? If not, where should I ask?
setup.ini is generated by a program called "upset". The current sources
are not available to the public since the program is not intended for
"roll-your-own-setup.ini" and the program is not something that I want
to receive patches for or questions about.
Older versions of the program are probably not kicking around out they
are not supported here.
If you want to generate a setup.ini use genini. If you find bugs, then
proposed patches will be thoughtfully considered as long as they aren't
band-aids.
cgf
--
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: How is setup.ini generated these days?
2011-04-17 21:19 ` Christopher Faylor
@ 2011-04-18 23:37 ` Jens Schweikhardt
2017-02-03 3:29 ` Steven Penny
0 siblings, 1 reply; 7+ messages in thread
From: Jens Schweikhardt @ 2011-04-18 23:37 UTC (permalink / raw)
To: cygwin
On Sun, Apr 17, 2011 at 01:35:01PM -0400, Christopher Faylor wrote:
...
# setup.ini is generated by a program called "upset". The current sources
# are not available to the public since the program is not intended for
# "roll-your-own-setup.ini" and the program is not something that I want
# to receive patches for or questions about.
#
# Older versions of the program are probably not kicking around out they
# are not supported here.
#
# If you want to generate a setup.ini use genini. If you find bugs, then
# proposed patches will be thoughtfully considered as long as they aren't
# band-aids.
For starters, the categories have apparently changed. The latest setup.exe
does not have Comm and Sound, but has gained Accessibility and Security.
--- genini.orig 2011-04-18 23:28:30.000000000 +0200
+++ genini 2011-04-18 23:32:56.000000000 +0200
@@ -289,9 +289,9 @@
BEGIN {
my @cats = qw'
- Admin Archive Audio Base Comm Database Devel Doc Editors Games
+ Accessibility Admin Archive Audio Base Database Devel Doc Editors Games
Gnome Graphics Interpreters KDE Libs Mail Math Mingw Net Perl
- Publishing Python Science Shells Sound System Text Utils Web X11
+ Publishing Python Science Security Shells System Text Utils Web X11
_obsolete _PostInstallLast
';
@main::categories{map {lc $_} @cats} = @cats;
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2017-02-03 4:12 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-04-17 4:10 How is setup.ini generated these days? Jens Schweikhardt
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
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).