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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=f2UlYuFHC4QWG7jgK4Kj863OW+keyX/v8I2v6w6CHme2F6mdHUOth
	DMd3t4afES8v7UmV9wrxhUrETpHHw3TGEUCW3kLP+CTwZDdFDXAvt75D0UC7OxfK
	uW4Y2d7rx5BO687NzAbbUZsYu63If6Eo8mOkq7iTMkrjSX4HOtdkIE=
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:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=+3v2SIXT3M7HO/q0Jugj+DjwBO0=; b=JrvjdKvjxhcZJZpfErj6wd1EJqi+
	VDMoOceUnXhgDHf3g50PQ4SyBa2rQof8n5B4cUxYCelvO38zIj3Rq7D/qL7XGDIF
	yiQ1P1H7cpfG8P9+HQorrCz3RGg3KHZIbLg9N8YE0jI9RVsvs+ArvfFDfCdufzI2
	TMg/7t3+UN5OIrQ=
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.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1+RnZsu+xkVaLROtaBCZERL
Date:	Thu, 23 Jan 2014 08:08:23 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: AdminCygwin Release
Message-ID:	<20140123130823.GB7177@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAO2ddnbtJ_mY1Yei6cx2GQO1dAWv=OV-cDVFO+aZD935MGQ7mA AT mail DOT gmail DOT com> <20140122023112 DOT GA4286 AT ednor DOT casa DOT cgf DOT cx> <CAO2ddnZM2FwzUSBJ2WHrBpQMe1sDt-8rWBpdJHEEzH3XCh3x4g AT mail DOT gmail DOT com> <20140122180852 DOT GA3153 AT ednor DOT casa DOT cgf DOT cx> <CAO2ddnaWAa0eeQZFQCEHzY+r2V75P1nnmW02fUeWLXsOuvzV1Q AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAO2ddnaWAa0eeQZFQCEHzY+r2V75P1nnmW02fUeWLXsOuvzV1Q@mail.gmail.com>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Jan 23, 2014 at 11:21:47AM +0100, BGINFO4X wrote:
>> On Wed, Jan 22, 2014 at 06:48:02PM +0100, 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
>>>>
>>>> Remember that you have to host all of the source code as well as the
>>>> binaries.
>>>
>>>Why do I neeed to host all the source code?  the sources are not
>>>necessary to produce my binaries ... I don't compile any ...
>>
>> Because that is how the GPL works.  If you provide binaries, you
>> provide sources.  This is basic stuff that you should know if you
>> are planning a forked Cygwin release or any sort of distribution
>> of open source binaries.
>
>Ok.
>
>"To the setup maintainers": it would be nice add "src" option on
>setup.exe, to get the source code of package with the command line.

Huh?  There is a source option in setup.exe.

>>>> I think it's more problem
>>>
>>>I see it as a "bash package" ready to be used by Win Admins ...
>>>
>>>than it is worth and is likely to cause
>>>> confusion within the Cygwin community.
>>>
>>>I don't see that point of view: This is not a fork of cygwin, only is
>>>a "Windows package of cygwin". It is "pure" cygwin.
>>
>> You're taking our packages, doing something with them and making them
>> available on another site.  i.e., you're forking our release.
>
>Ok. Thanks for your appointment.
>
>> You're actually treading on thin ice here since you are trying to get
>> help for a release that is not the subject of this mailing list.  That
>> makes this whole discussion pretty much off-topic.
>
>Yes, I'm sorry. I will move the discussion to cygwin-talk list if you
>don't mind.

Actually, I do mind.  The cygwin-talk list isn't intended to be a forum
to discuss other cygwin releases.

>> And that's another issue.  We definitely will not be providing support
>> for anyone who wanders in here looking for help with problems they
>> encounter with your packages.
>
>I TOTALLY agree with this.

You may agree with this but that won't stop people from being confused.

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.

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.

cgf

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