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:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=WcsFnpQho8jUoskY
	9EH7pNPUj+AAklf5x81pTEpSl/e4t99d05OmYIaUopB9LNpchQecYd514pDXLO9z
	b3uVksJhFvmno5IcqjFcd9wvMFbyC7VJQbl3jGIcLKqcl85CbTC5eDrJ4p54iAE8
	z8ymHFTJiY2c7C78wfgy4IL3AN4=
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:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=bwQusyWIE7pdPfpyGBxZ3K
	OxYZA=; b=HKiOqGzyHunaE3hqgjkYuUx8LxQpLPJV5eCe6o97KP8AaXFRpA3mlu
	k20mSjRV3nnBpLWDbUGWi6ZovKlhh1/OA38LNZb9lMGPxvGKTvemxyVCJbw/Ieyu
	YLxpF/dYw3vB/E7zzcePUiQZBqFVMyF7gFqODhbA1PBZEVvu0r56M=
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.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	vms173025pub.verizon.net
Message-id:	<52DEDDC5.2070703@cygwin.com>
Date:	Tue, 21 Jan 2014 15:51:17 -0500
From:	"Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to:	cygwin AT cygwin DOT com
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: AdminCygwin Release
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>
In-reply-to:	<CAO2ddnb+Vfn+199r-qqmPF=tL5XeEmYO2Qmn+=d2sKw4QK2Ong@mail.gmail.com>

On 1/21/2014 2:52 PM, BGINFO4X wrote:
>>> Hello everyone,
>>>
>>> I'm trying to create a "Small Admin Cywgin relase", called AdminCgwin.
>>> If it works, I will upload to sourceforge.
>>>
>>> These are the main lines:
>>>
>>> 1- Create an installation windows package (.msi) with WIX.
>>>
>>> 2- Default Installed packages: base + admin + apt-cyg.
>>> The remaining packages should be installed via apt-cyg
>>>
>>> 3- Customize /etc/profile to use folders outside the "Installation
>>> folder".  Folders like Temp, Home must be out "cygwin installation
>>> folder".
>>>
>>> 4- Customize Cygwin.bat to start in a folder with spaces.
>>>
>>> 5- Launch a custom action after msi installation, to execute
>>> postinstall : 000-cygwin-post-install.sh.
>>> I will try to reset /etc/passwd & /etc/group to the "new SAM machine".
>>>
>>> Do you see any drawback that could broke cygwin? Do you have any
>>> recommendation? I really appreciate your comments.
>>
>>
>> I see lots of potential issues with something like this:
>
> But .... any issue related to "broke cygwin behaviour"?

Certainly this would have the potential to interfere with any existing
Cygwin installation.  Also, it's not clear to me that the post-install
scripts for the packages you're bundling in the MSI will be run.

>> not the least of which is that it will be a burden for you to keep up-to-date.
>
> I will not try to keep up-to-date. Only "major releases" will produce
> a new .msi. Upgrades should be done via "apt-cyg".

OK.  Obviously, depending on your audience, the multiple ways of installing
and upgrading may be a stumbling block.  Also, a subsequent installation of
Cygwin via setup*.exe could lead to problems.

>> I think the question you have to ask yourself is what problem are you
>> trying to solve and can it be done within the context of setup*.exe
>> and the existing packages?
>
> 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.

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

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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