From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Hung setup-x86_64.exe after parsing setup.ini
Date: Wed, 14 Aug 2019 17:33:00 -0000 [thread overview]
Message-ID: <87zhkbbqjh.fsf@Rainer.invalid> (raw)
In-Reply-To: <003aa1a12e604bcca88f42a3a8aa41c9@spb.rpkb.ru> (=?utf-8?B?ItCS0LXRgdC90LjQvSDQrtGA0LjQuQnQkNC70LXQutGB0LDQvdC00YDQvtCy?= =?utf-8?B?0LjRhyIncw==?= message of "Mon, 12 Aug 2019 09:44:44 +0000")
Веснин Юрий Александрович writes:
> It's definitely a bug. What's the proper way to fix it?
It's not a fix, but for starters you could create a bunch of smaller packages.
> Addition:
> @ rdc-deps
> sdesc: "RDC's devel dependencies"
> ldesc: "RDC's devel dependencies"
> category: Base
> requires: ca-certificates gcc-core gcc-g++ git gnupg libftdi1 lynx make openssh python python27 python27-pip python38 python38-pip subversion vim wget
> version: 0.1-1
> install: x86_64/release/rdc-deps/rdc-deps-0.1-1.tar.xz 10240 2aaf7929c7d5299e2613f5a9eb18d7a644c81d0da7a6fba93069c83a490ec798941043a8ed8bb95b28ce21179e987e1f04f372a891a5918b40db6f612276f6e4
> source: x86_64/release/rdc-deps/rdc-deps-0.1-1-src.tar.xz 108 da016ecd9ac6dd3ecd1a65b80c2728db59bccd9ca5e6b54888f02398e3f97a90d1bae3bef85f0eb0950c07734bf3e191fb679fc39527205ba0520009ca4769d2
> depends2: ca-certificates, gcc-core, gcc-g++, git, gnupg, libftdi1, lynx, make, openssh, python, python27, python27-pip, python38, python38-pip, subversion, vim, wget
>
> @ rdc-tools
> sdesc: "RDC's toolchain"
> ldesc: "RDC's toolchain"
> category: Base
> requires: rdc-deps
> version: 1.1.1-1
> install: x86_64/release/rdc-tools/rdc-tools-1.1.1-1.tar.xz 1378576256 5b15397950db4f95e3e0560a5c9183b3811e821cfb183db1bf93a411e01e5bb4b86825a28f8121389422ffd7e9f12eef88b22560f8c30b2beb5fae230c738332
> source: x86_64/release/rdc-tools/rdc-tools-1.1.1-1-src.tar.xz 108 da016ecd9ac6dd3ecd1a65b80c2728db59bccd9ca5e6b54888f02398e3f97a90d1bae3bef85f0eb0950c07734bf3e191fb679fc39527205ba0520009ca4769d2
> depends2: rdc-deps
None of this should have category Base. Use your own category and
install by category in setup.exe.
I hope it's obvious that the empty rdc-deps package is currently useless
and you could just list the deps right here. But you could depend on
non-empty pakcages of your own and therefore split this hguhe thing into
a number of packages that have more manageable sizes.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
--
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
prev parent reply other threads:[~2019-08-14 17:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 9:44 Веснин Юрий Александрович
2019-08-13 11:40 ` Jon Turney
2019-08-13 16:57 ` Веснин Юрий Александрович
2019-08-13 17:27 ` Jon Turney
2019-08-14 10:05 ` Веснин Юрий Александрович
2019-08-14 17:33 ` Achim Gratz [this message]
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=87zhkbbqjh.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).