From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: How portable (relocatable) is a Cygwin installation?
Date: Thu, 10 May 2018 17:43:00 -0000 [thread overview]
Message-ID: <87o9hnfqvs.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAM-5HMtk-0xo9L+8HWZmVjhXQxKGaG8_NS8NKWwOed+gdn806g@mail.gmail.com> (Andy Li's message of "Thu, 10 May 2018 08:08:29 +0800")
Andy Li writes:
> We are looking for an easy way to distribute an OCaml development
> enviroment based on Cygwin.
You're asking to package up a complete software ecosystem on top of a
POSIX emulation layer on top of a non-POSIX OS. Any which way you slice
it, this will not fit the "easy" qualification you put there.
> Someone has an idea of installing all the necessary packages and zip
> the whole Cygwin installation directory and distribute the resulting
> archive.
Yes, there's always someone with an idea and no, I don't blame them.
I've once thought it might be a neat idea to install Cygwin into a
virtual HD image and distribute it among multiple machines this way.
Even though I think I've enjoyed much tighter control about those
machines than you seem to be able to, it turned out to be impractical.
> Is it a good idea? Is the installation path written in a Cygwin
> installation somewhere that may need to be updated when relocating? Is
> there any registry entry or env var required for a Cygwin installation to
> work?
Provide your own local Cygwin mirror and an install script to
consistenly chose the same set of packages. Make sure your users update
when you update the mirror.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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-05-10 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 1:19 Andy Li
2018-05-10 1:22 ` Brian Inglis
2018-05-10 11:49 ` R0b0t1
2018-05-10 17:43 ` Achim Gratz [this message]
2018-05-10 18:42 ` Soegtrop, Michael
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=87o9hnfqvs.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).