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=mRQ9+YGGP6PkkWGW
	c8dF8I1RQ0q+7ie4mNEdMTjRAZoxNhG2XPLbN+FjzUNIhzQmUZ5QrrN72Uz3eBSl
	BSwNtQZY2LLTszxsyv7Vy7Ak120EBloVFh158gpiajpBvftf4ceYXmPBFpYjE7eR
	1QvCmlwSg8IRG4E/+xQ4wy6IfKQ=
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
Message-id: <52E00A26.4080309@cygwin.com>
Date: Wed, 22 Jan 2014 13:12:54 -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> <52DEDDC5 DOT 2070703 AT cygwin DOT com> <CAO2ddnaeeH_j4z01979_bx9GM2Pcv5kpooLTxvXGH6frygqsGg AT mail DOT gmail DOT com>
In-reply-to: <CAO2ddnaeeH_j4z01979_bx9GM2Pcv5kpooLTxvXGH6frygqsGg@mail.gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 1/22/2014 12:43 PM, BGINFO4X wrote:
> -> 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...

Yes, if it is managed properly.  If not, bad things can still happen
which will most likely lead to confusion and questions, most probably
directed to this list.  This leads to another aspect you would have to take
into account with your distribution - how will you support it and how
will your users know to consult your support avenues rather than the
ones available at cygwin.com?

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

Yes, I understand you fine, thanks.  So it sounds like you're mostly
interested in providing bash and other default Cygwin utilities to
admins.  In addition, you want to give them BGINFO4X.  From looking at
BGINFO4X at the SF site, it looks like another viable option would be to
create a BGINFO4X package for Cygwin.  Then there would be no conflict with
existing or future installs of Cygwin, the install and upgrade mechanism
would always be the same (setup*.exe), it would be a supported package
within this forum (through you), and you could even provide a separate
install script leveraging setup*.exe to install only the packages you want
to promote (through your own site) if you want.  See the link below
if you're interested in exploring this option in more detail:

<http://cygwin.com/setup.html>

I think this approach would allow you to reach the goals you stated above
and fits in with the normal Cygwin infrastructure, making things easier
for everyone.

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