From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: distributing preconfigured cygwin
Date: Fri, 17 Aug 2018 19:49:00 -0000 [thread overview]
Message-ID: <87a7pku9sl.fsf@Rainer.invalid> (raw)
In-Reply-To: <20180817094154.GB9924@rus.uni-stuttgart.de> (Ulli Horlacher's message of "Fri, 17 Aug 2018 11:41:54 +0200")
Ulli Horlacher writes:
>> If they can follow your current instructions, they can surely start some
>> script that does this correctly?
>
> I do not have a script which installs all needed packages.
So write one.
> This install script must first download the cygwin base package, install
> it and then run setup with all needed cygwin packages.
You might want to have at least look at the help output from setup if
not even read the documentation: setup can do that all in one go.
> But at the very beginning, I do not have a shell at all?
Use either CMD or PowerShell as appropriate.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
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
next prev parent reply other threads:[~2018-08-17 18:29 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 11:50 running self compiled 32 bit binary on 64 bit Windows? Ulli Horlacher
2018-06-06 12:05 ` Markus Hoenicka
2018-06-06 16:05 ` Andrey Repin
2018-06-06 16:42 ` Ulli Horlacher
2018-06-06 17:50 ` Andrey Repin
2018-06-06 16:25 ` Soegtrop, Michael
2018-06-06 16:29 ` Soegtrop, Michael
2018-06-06 17:50 ` Andrey Repin
2018-06-06 20:26 ` cyg Simple
2018-06-06 22:05 ` Andrey Repin
2018-06-08 13:31 ` Ulli Horlacher
2018-06-08 13:37 ` cyg Simple
2018-06-08 13:45 ` Ulli Horlacher
2018-06-08 13:52 ` Soegtrop, Michael
2018-06-08 13:56 ` cyg Simple
2018-06-08 16:50 ` Andrey Repin
2018-06-08 18:20 ` Csaba Raduly
2018-06-08 13:43 ` Soegtrop, Michael
2018-06-08 13:52 ` Ulli Horlacher
2018-06-08 16:50 ` Andrey Repin
2018-07-09 0:21 ` Ulli Horlacher
2018-07-09 2:20 ` Andrey Repin
2018-07-09 6:22 ` Brian Inglis
2018-07-09 6:29 ` Ulli Horlacher
2018-07-14 15:41 ` Achim Gratz
2018-08-17 10:29 ` distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?) Ulli Horlacher
2018-08-17 10:58 ` distributing preconfigured cygwin john doe
2018-08-17 17:05 ` distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?) Andrey Repin
2018-08-17 19:49 ` Achim Gratz [this message]
2018-08-29 11:09 ` distributing preconfigured cygwin Ulli Horlacher
2018-08-29 11:31 ` Andrey Repin
2018-08-29 12:08 ` john doe
2018-08-30 12:35 ` running self compiled 32 bit binary on 64 bit Windows? Ulli Horlacher
2018-08-30 13:55 ` Marco Atzeri
2018-08-30 13:59 ` Andrey Repin
2018-08-30 19:20 ` Ulli Horlacher
2018-08-30 21:06 ` Ulli Horlacher
2018-08-31 8:58 ` Andrey Repin
2018-08-31 8:35 ` Achim Gratz
2018-06-08 13:43 ` Ulli Horlacher
2018-06-08 13:19 ` Ulli Horlacher
2018-06-08 13:28 ` Soegtrop, Michael
2018-06-08 13:34 ` cyg Simple
2018-06-08 13:54 ` Ulli Horlacher
2018-06-08 19:05 ` Achim Gratz
2018-06-06 20:13 ` cyg Simple
2018-06-08 13:42 ` Ulli Horlacher
2018-06-08 17:44 ` Brian Inglis
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=87a7pku9sl.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).