X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=lN
	NItzMj5Zyp4JqXc88mWWmseX+djAbvmDc1sLeJufPMPmdCzIzqG3m3RGkja3ETmb
	g+K0aJlMQI24Tfvq7K15pajrWhBNXOZIwZGU3t3RwK1zsw8d028QiArn2Rr5LfIa
	grs6DrFRF4dMAfO52/MSmRHykJ37XeXbqpLsm8/e0=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; s=default; bh=6c6EqB+b
	M1WbS05EsSJtOK8inOA=; b=sLoe+B3zzL/gDHkPRdzx2UgVpQePnWv2/fSA0T3i
	3/iH5aTdKlfKzRTndDDG2Y+lmP3hFbmmJWw971W4XCWkbmblyghmRMEjjWzw+/kC
	uR2ZoYfGe96jWXPZoe2IF51HFoCq1Yjvh1SYFMnZCGNo4K/f71EdxcFAFKkzffu+
	kDU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-ob0-f182.google.com
MIME-Version:	1.0
X-Received:	by 10.60.246.164 with SMTP id xx4mr53070oec.25.1390412594721; Wed, 22 Jan 2014 09:43:14 -0800 (PST)
In-Reply-To:	<52DEDDC5.2070703@cygwin.com>
References:	<CAO2ddnbtJ_mY1Yei6cx2GQO1dAWv=OV-cDVFO+aZD935MGQ7mA AT mail DOT gmail DOT com> <52DEBB76 DOT 2040004 AT cygwin DOT com> <CAO2ddnb+Vfn+199r-qqmPF=tL5XeEmYO2Qmn+=d2sKw4QK2Ong AT mail DOT gmail DOT com> <52DEDDC5 DOT 2070703 AT cygwin DOT com>
Date:	Wed, 22 Jan 2014 18:43:14 +0100
Message-ID:	<CAO2ddnaeeH_j4z01979_bx9GM2Pcv5kpooLTxvXGH6frygqsGg@mail.gmail.com>
Subject:	Re: AdminCygwin Release
From:	BGINFO4X <bginfo4x AT kztsoftware DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes

-> Larry wrote:

> Certainly this would have the potential to interfere with any existing
> Cygwin installation.

I have read that you can have more than one installation of cywgin in
a single machine...

> Also, it's not clear to me that the post-installscripts for the packages you're bundling in the MSI will be run.

Yes, I'm sure that this can be done.

>> Basically, the main idea is:
>>
>> 1- Fast installation of the package (msi). Can be also installed
>> massively via Active Directory or specialized programs.
>
>
> OK, I'll take your word that your MSI package is "better" in this
> respect.
>
>
>> 2- Fast administration of a windows machine once installed.
>
>
> Is there really a difference in usage once you've installed?  Seems to
> me there should be no difference but I don't know what the particulars are that you're thinking of.

No, no difference should be there. Once installed It will be a "normal
cygwin installation".

The idea of the release is to have a "packaged bash", so Windows
administrators can start to play on it.


>> 3- Base platform for integration with other programs, like BGINFO4X or
>> others.
>
>
> Again, it's not clear to me how the mechanism for installing Cygwin affects
> this, unless you see your MSI as growing to encompass these other programs
> as well.  If so, then your MSI has a value beyond installing Cygwin so
> that's one advantage of your approach.  I will admit, however, that I am
> no expert at building MSI installers so I can't make suggestions of
> alternative ways to structure an MSI install to leverage Cygwin installer
> and install other software as well.

Yes, this is an option: create a bundle with differnt MSIs
(AdminCygwin.MSI + BGINFO4X.msi),

Nowadays , what I do is: install MSYS + install BGINFO4X -> create BGINFO4X.msi.

What I'm trying is to substitute MSYS by CYWGIN ...

... and I thought: why don't create a "base AdminCygwin package"? I
have practically all the work done ...

So what I will try is:
create AdminCygwin.MSI -> install AdminCygwin.MSI -> install BGINFO4X
inside "AdminCygwin" -> create a new BGINFO4X.msi.

I hope that you understand me. English is not my native language.

Thanks a lot for your time.

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

- Raw text -