DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=kDKlcACJi/d9V+rJ
	P7FpvQXNqrgsqFC5+gt0TP4Qp18CzADO4d3o06ryM1pPH3MIrnjXSqd+ZNmdTwql
	nquWvy50tUOknhO+cYyNX0kBBSQDBX/LyvaMo4Xyoi41KBP5/yG9qyEb/DD1An1x
	5JojNajWItX4Vbv6gbYVtzcrtcw=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: How portable (relocatable) is a Cygwin installation?
To: cygwin AT cygwin DOT com
References: <CAM-5HMtk-0xo9L+8HWZmVjhXQxKGaG8_NS8NKWwOed+gdn806g AT mail DOT gmail DOT com>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <35bbce66-d74a-357e-785d-973a956f4723@SystematicSw.ab.ca>
Date: Wed, 9 May 2018 19:19:35 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAM-5HMtk-0xo9L+8HWZmVjhXQxKGaG8_NS8NKWwOed+gdn806g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 2018-05-09 18:08, Andy Li wrote:
> We are looking for an easy way to distribute an OCaml development
> enviroment based on Cygwin. Someone has an idea of installing all the
> necessary packages and zip the whole Cygwin installation directory and
> distribute the resulting archive.
> 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?

Others use that approach, which generates many posts asking about find_fast_cwd
warnings, due to lack of Cygwin updates and Windows update incompatibilities.
No. Yes. Yes.
How good is your organization's Windows app packaging, distribution, deployment,
and installation system e.g. SCCM infrastructure?

Rather than deal with possible existing Cygwin installs, internal details which
may change, initial install actions, package postinstall script effects, and dll
rebasing, it may be better to distribute a zip, or use a network share or web
server, to provide a local package archive with the
{noarch,x86{,_64}}/release/<package>/ directories and contents including setup
exe, ini, distributed .tar.xz packages, and install on each system using Cygwin
setup from that location, instead of an official network mirror.
The install could be a scripted unattended setup run: check what the web docs
say about using local archives, and unattended setup.
You could standardize on Cygwin root e.g. C:\cygwin{32,64}\ and local package
archive location of C:\cygwin{32,64}\var\cache\setup\, or a network share or web
server equivalent of the latter.
Updated copies of the setup exe, ini, packages, and all dependencies can be
added to that local archive to allow synchronized updates using Cygwin setup.
You will have to track and save all Cygwin updates, and decide when you need or
want to release updates for your custom distro.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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