This is the mail archive of the
mailing list for the Cygwin project.
Re: using genini for split packages [Was: [RFU] tidy-20090325-1]
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 15 Nov 2010 10:41:46 -0500
- Subject: Re: using genini for split packages [Was: [RFU] tidy-20090325-1]
- References: <4C9BB424.email@example.com> <20100924090942.GA18461@calimero.vinschen.de> <4C9CD875.firstname.lastname@example.org> <4CDE4CEE.email@example.com>
- Reply-to: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
On 11/13/2010 3:31 AM, Lapo Luchini wrote:
> Charles Wilson wrote:
>>>> PS: I wasn't able to compile setup.ini locally using genini, is it
>>>> possible for split packages?
>>> Yes, it is. Did you use the --recursive option?
>> And, of course, the files need to be arranged as Corinna indicated
>> above, or genini will croak just like upset would.
> It still seems to croaks, and is not producing the source link:
Here's what I do:
after cygport puts everything in the foo-$VER-$REL/dist/ directory, I
cp -a foo /tmp/MY-TEST-REPO/release/
genini --recursive release > setup.ini
Be sure you're using the latest version of genini. There are some cases
where genini is happy, but upset won't be -- and vice versa. :-(
However, in most cases using genini is a pretty good validator.