From: Jon Turney <jon.turney@dronecode.org.uk>
To: Sunny Lin <sunny.khh@gmail.com>, cygwin@cygwin.com
Subject: Re: Problem with mksetupini
Date: Wed, 15 Feb 2017 14:09:00 -0000 [thread overview]
Message-ID: <3c228f7f-8af0-fbd6-8b60-ca8d0736b264@dronecode.org.uk> (raw)
In-Reply-To: <CAL93U-KtEvR+D1uraT-Q+QUOutZJeBBn3mWsF9rUUo9YbkgSMw@mail.gmail.com>
On 15/02/2017 07:51, Sunny Lin wrote:
> Hi all,
>
> I encountered a problem and hope someone here can help me through.
>
> I need to build a 32-bit Cygwin distribution with customized packages.
> I have calm package installed. I am learning to use mksetupini to
> create a setup.ini file. I use commands similar to the following but
> always generate an INI file with only a header, no package information
> in the file.
>
> mksetupini --arch x86 --inifile=setup.ini --releasearea=.
>
> I followed instruction in the following link and got the same result.
> https://cygwin.com/package-server.html
Reading over that, it looks like step 2 is in need of a bit of updating
and might have led you astray.
The directory you are pointing to as releasearea should contain x86/,
x86_64/ and noarch/ directories, which should contain a release/
directory, which should contain the various package directories and
subdirectories.
If that layout isn't followed, mksetupini won't be able to find the
packages and thus they won't appear in the output setup.ini
Failing that, perhaps running mksetupini with the --verbose flag will
give a bit more insight into what is happening?
--
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 prev parent reply other threads:[~2017-02-15 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 7:51 Sunny Lin
2017-02-15 14:09 ` Jon Turney [this message]
2017-02-15 15:13 ` Jon Turney
[not found] ` <CAL93U-JX3_kLkqS58BFrp5RzBWnBoU0zaVLrotyNjDaCdOar0A@mail.gmail.com>
2017-02-20 15:18 ` Jon Turney
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=3c228f7f-8af0-fbd6-8b60-ca8d0736b264@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=sunny.khh@gmail.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).