From: Ulli Horlacher <framstag@rus.uni-stuttgart.de>
To: cygwin@cygwin.com
Subject: distributing preconfigured cygwin (was: running self compiled 32 bit binary on 64 bit Windows?)
Date: Fri, 17 Aug 2018 10:29:00 -0000 [thread overview]
Message-ID: <20180817094154.GB9924@rus.uni-stuttgart.de> (raw)
In-Reply-To: <87d0vp7uth.fsf@Rainer.invalid>
On Sat 2018-07-14 (16:31), Achim Gratz wrote:
> >> You have to install Cygwin, not "transfer".
> >
> > I have several 100 users, none of them is able to install cygwin and
> > the packages they need the official way, they are way to *CENSORED* for
> > this job :-}
>
> 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.
> > I give them my preconfigured cygwin.zip (or cygwin64.zip) and tell them to
> > unpack it in C:\
> >
> > http://fex.belwue.de/usecases/cygwin.html
>
> Whatever you call it, it's still cludgey nonsense that might or might
> not work. Only when it's not working your users will really be unable
> to figure out what to do since they won't even know what is failing.
So far, it has worked for all my users. No one is complaining.
> script that calls setup to install it and any other packages you need
> (if not already installed by way of dependency). Setup can deal with
> multiple package repositories, so you can use one of the official
> mirrors as the primary package repository and only provide your package
> as an add-on repository (like cygwin ports does).
How do I write such a script?
Is there documentation/examples about this?
This install script must first download the cygwin base package, install
it and then run setup with all needed cygwin packages.
But at the very beginning, I do not have a shell at all?
--
Ullrich Horlacher Server und Virtualisierung
Rechenzentrum TIK
Universitaet Stuttgart E-Mail: horlacher@tik.uni-stuttgart.de
Allmandring 30a Tel: ++49-711-68565868
70569 Stuttgart (Germany) WWW: http://www.tik.uni-stuttgart.de/
REF:<87d0vp7uth.fsf@Rainer.invalid>
--
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 9:41 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 ` Ulli Horlacher
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 ` Ulli Horlacher [this message]
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 ` distributing preconfigured cygwin Achim Gratz
2018-08-29 11:09 ` 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: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=20180817094154.GB9924@rus.uni-stuttgart.de \
--to=framstag@rus.uni-stuttgart.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).