This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: AdminCygwin Release
- From: BGINFO4X <bginfo4x at kztsoftware dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 23 Jan 2014 16:35:47 +0100
- Subject: Re: AdminCygwin Release
- Authentication-results: sourceware.org; auth=none
- 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>
>>> 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?
>>> 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.
At least on my opinion, as an administrator, has very sense to have a
"bash windows" in a "nerd-msi" installable form.
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.
Thanks a lot for your time.
> 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
>
--
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