From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 62979 invoked by alias); 10 May 2018 01:19:41 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 62970 invoked by uid 89); 10 May 2018 01:19:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=mirror, sk:incompa, H*R:D*ca, _64 X-HELO: smtp-out-no.shaw.ca Received: from smtp-out-no.shaw.ca (HELO smtp-out-no.shaw.ca) (64.59.134.12) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 10 May 2018 01:19:38 +0000 Received: from [192.168.1.100] ([24.64.240.204]) by shaw.ca with ESMTP id GaF5fzwYZvB5RGaF6fBDKC; Wed, 09 May 2018 19:19:36 -0600 X-Authority-Analysis: v=2.3 cv=PvS9kTE3 c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=AsBeeLkhoQnVERyA_XkA:9 a=QEXdDO2ut3YA:10 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: How portable (relocatable) is a Cygwin installation? To: cygwin@cygwin.com References: From: Brian Inglis Message-ID: <35bbce66-d74a-357e-785d-973a956f4723@SystematicSw.ab.ca> Date: Thu, 10 May 2018 01:22:00 -0000 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: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfCSP2yoe8JHQnHCi0igsKIq2W9TIf0p1/CevaftsRVxMQmY/ke6IRgA77FK23KoWUxU336hZhe1xR07QuR/iO3bFQaY8LcjGkkWQebBhs3eoL4YFny13 rePOVuNDoBJg3i66nIJpn+AZ/LCjzusJ+VR0XyaDrxitfWVc/7gsQETHyBKMNM7FCYeyu75AW1JrYw== X-IsSubscribed: yes X-SW-Source: 2018-05/txt/msg00124.txt.bz2 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// 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