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=u5
	7tSDksBekHp0pL4NBz1vAMoQjmBQVjnegWnZAcrclsNCdLSeU2FxEcIq+AZ2WqOc
	xigB9mQrJ07KZKYBqYyz//FeSdi3URe2q4ycgoFiqVIykHLRBCXeQ/jfG1Rpv4w4
	f8kOhBkIefs+bHesCkui16AEtSaWr18SBzAU0JHMw=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <181748041.20140123205833@mtu-net.ru>
References: <CAO2ddnbtJ_mY1Yei6cx2GQO1dAWv=OV-cDVFO+aZD935MGQ7mA@mail.gmail.com>	<20140122023112.GA4286@ednor.casa.cgf.cx>	<CAO2ddnZM2FwzUSBJ2WHrBpQMe1sDt-8rWBpdJHEEzH3XCh3x4g@mail.gmail.com>	<20140122180852.GA3153@ednor.casa.cgf.cx>	<CAO2ddnaWAa0eeQZFQCEHzY+r2V75P1nnmW02fUeWLXsOuvzV1Q@mail.gmail.com>	<20140123130823.GB7177@ednor.casa.cgf.cx>	<CAO2ddnbXX_556nv8dsUXDc1UNSCpmRoKjC6Su1GDW_NptiHQyQ@mail.gmail.com>	<181748041.20140123205833@mtu-net.ru>
Date: Fri, 24 Jan 2014 11:59:57 +0100
Message-ID: <CAO2ddnabUDQiq0=XrSMLh6rvgzVB8GFVN+rZbnZeZ8BgSjdOCw@mail.gmail.com>
Subject: Re: AdminCygwin Release
From: BGINFO4X <bginfo4x@kztsoftware.com>
To: Andrey Repin <cygwin@cygwin.com>
Content-Type: text/plain; charset=ISO-8859-1

Thanks Andrey for your reply.  I prefer to send a direct mail to you
to respond, they are a little "angry".

2014/1/23 Andrey Repin <anrdaemon@yandex.ru>:
> Greetings, BGINFO4X!
>
>>> I still think this is a bad idea.  I know what you're trying to do.  You
>>> are basically trying to provide a solution using tools that you more or
>>> less understand rather than trying to work within the existing
>>> (admittedly crude) release structure to provide benefit to everyone who
>>> uses Cygwin.
>
>> I'm sorry, but this is not true: I only want to give comunity a "base
>> package" of something that I already have.
>
> It is Cygwin providing a base package, that you have.
> The key word is "providing", means, it's already available to the community.
> What you want to do is to repackage and redistribute what is already packaged
> and distributed. Doing fool's work, don't you think?
>
>> At least on my opinion, as an administrator, has very sense to have a
>> "bash windows" in a "nerd-msi" installable form.
>
> I don't understand your inclination with MSI first

It is simple:

a) give setup.exe to a non-tech "man/woman" and tell him/her: please,
can you install bash? And see what happens ... 95% will fail.

b) give for example bginfo4x.msi to a non-tech "man/woman" and tell
him/her: please, can you install it? And see what happens ... 95% will
succeed.

>, and Cygwin does NOT play by Windows rules, second.

IMHO: This is a problem that "cygwin people" should solve.

> Cygwin, per definition, adapt Linux, not Windows, paradigm, and may be VERY destructive, if not installed correctly.

I know it.

Thanks 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