X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sat, 12 Apr 2008 10:35:22 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Embedded packaging of cygwin without installation
Message-ID: <20080412083522.GA23852@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <013901c89436$214ba6d0$63e2f470$@com> <47F535CA DOT 11611312 AT dessent DOT net> <025701c89bf7$bc433e50$34c9baf0$@com> <48001F08 DOT 4020007 AT cwilson DOT fastmail DOT fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <48001F08.4020007@cwilson.fastmail.fm>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Apr 11 22:31, Charles Wilson wrote:

> [Good ol' licensing fine print removed]

>> For me it would be okay, if I could detect if there is a installed cygwin
>> with my needed utils (bash, grep, sed, awk, read...)
>> For now my only idea was to package it with my distribution.
>> So here my new suggestion:
>> 1.    is cygwin installed?
>> 1.1.  yes, setup the environment-variables to use the installed one
>> 1.1.1 are the needed tools installed?
>> 1.1.2 no, run cygwin-setup and preselect the additionally needed tools
>> 1.2.  no, run cygwin-setup with the preselected needed tools
>> Is this possible to realize?
>
> That sounds almost ideal (to me, but I'm no authority). 

Authoritative ACK, including the "almost".

> [...]
>
> (1) (a) Just create a setup.exe-compatible package for your tool
>     (b) create a cygwin "release" directory on a website of your control
>     (c) populate it with all the cygwin packages (including -src) you want 
> to include in your mini-distro PLUS all of the dependencies for those 
> packages
>     (d) create a setup.exe-compatible setup.ini script that describes the 
> packages available on your site (use 'genini')
>     (e) tell people to use setup.exe, with "custom mirror" set to your 
> site, and 'install all'.  (FWIW, this is what I did for an internal 
> customized cygwin distro for my employer)  If they already have cygwin, 
> and/or newer versions of some of your copied packages, they get to keep 
> their newer versions, and just pull in your special package, and any other 
> requirements they don't already have.
>     (f) alternatively, if setup.exe has cmdline args to set a specific 
> mirror choice (I don't know), give your user a batch file that 
> automatically runs setup.exe with --some-option your-mirror.

That's the second best way, really.  The best way is to become a Cygwin
package maintainer for your special packages and put them into the distro.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/