DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=mnEqnyzhDWoq27NJ
	3700Pn5MNE0cIUTFSeeMsBM4F03a0gnz+3t8ndIs8gDKVqQH8PDOH361k2ReWg+N
	N2NWfNife4wL567GxnbW1W72q/0jEF1Xflfeug1+DOECSexgoHVV7UWi7OYetgUM
	QaGCT7PKmTc3+VgZeXKiHvACRcQ=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 23 Jan 2014 20:58:33 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: Andrey Repin <cygwin@cygwin.com>
Message-ID: <181748041.20140123205833@mtu-net.ru>
To: BGINFO4X <bginfo4x@kztsoftware.com>, cygwin@cygwin.com
Subject: Re: AdminCygwin Release
In-Reply-To: <CAO2ddnbXX_556nv8dsUXDc1UNSCpmRoKjC6Su1GDW_NptiHQyQ@mail.gmail.com>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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, and Cygwin does NOT play
by Windows rules, second.
Cygwin, per definition, adapt Linux, not Windows, paradigm, and may be VERY
destructive, if not installed correctly.

> But if you don't agree, don't mind: I can upload my next BGINFO4X
> release without creating any "AdminCygwin release".

> There is no problem, but I thought that it could be useful to others.

>> We sometimes get people here who think they have to fork Cygwin because
>> they understand some subset of something on their own and don't or can't
>> grok the big picture well enough to try to make changes within the
>> release.  There is that + the need some people have of being a
>> recognized "Project lead".  Believe me, the glory in that title cannot
>> be underestimated.  It's a heady experience.

> I'm sorry again, but If I understand you (not 100% sure), I don't want
> to be recognized.

What you want to be is not a point of discussion.
What you are trying to do - that's what matters.
Instead of learning the tools available (setup and cygport i.e.), you are
trying to produce a solution using tools you [think you] understand (MSI).

P.S.
I think many readers of the list would appreciate, if you stop quoting the
people's templates.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 23.01.2014, <20:46>

Sorry for my terrible english...


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