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=dwJl+4wL7THJ0c8+RamGs1wfHg/Q2jLQTaRgyRkIqKyPdjq5k6QK1
	75wS0e9ZcGuoWRopjnlWWhzkQMansBaD+WzqGUMF3bhDKOTNudG5aLVMEQkT/pfM
	dio6iYvxVYQnwVriT7vM2mqT+nMCPiwwdusebqzPPKzHIXrBvhBwCg=
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
Date: Wed, 22 Jan 2014 13:08:52 -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: <20140122180852.GA3153@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAO2ddnZM2FwzUSBJ2WHrBpQMe1sDt-8rWBpdJHEEzH3XCh3x4g@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

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.

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

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.

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.
--
Christopher Faylor			spammer? ->	aaaspam AT sourceware DOT org
Cygwin Co-Project Leader				aaaspam AT duffek DOT com

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