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=gD98742apY9v4CX5npKTB0E5kg/JRcn8IyLmBxjngmZDZbflGh7Ot
	jx2IAEUT/txtp5Aa66g6/DRK/9w6sa0WJFwT9iIw3XRf5zKgHSD4p84MD+IcgtRM
	MTK35jbThEqZVCaE0PlTgPS7tiTiB/MBYyg2AekvIddQw2Ma5JPuNc=
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: Thu, 23 Jan 2014 14:52:53 -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: <20140123195253.GA1417@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> <20140123130823 DOT GB7177 AT ednor DOT casa DOT cgf DOT cx> <CAO2ddnbXX_556nv8dsUXDc1UNSCpmRoKjC6Su1GDW_NptiHQyQ AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAO2ddnbXX_556nv8dsUXDc1UNSCpmRoKjC6Su1GDW_NptiHQyQ@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Thu, Jan 23, 2014 at 04:35:47PM +0100, BGINFO4X wrote:
>>>> 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.
>
>Well, is there any cygwin-list to talk about this?

No.  The cygwin mailing lists are intended to talk about the version of
Cygwin distributed and maintained by the people responsible for Cygwin.

Even cygwinports has its own mailing list.

>>>>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.
>
>I'm sorry, but this is not true: I only want to give comunity a "base
>package" of something that I already have.

You want to fork Cygwin and make it available via an alternate install
method rather than try to work to provide something like that via
setup.exe.

I think you've explained what you want to do enough not.  I'm officially
calling this off-topic.  I don't think there is any reason to discuss
this any further.

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