This is the mail archive of the
mailing list for the Cygwin project.
Re: pdksh installation
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 3 Mar 2003 11:46:46 -0500
- Subject: Re: pdksh installation
- References: <email@example.com> <Pine.GSO.firstname.lastname@example.org> <20030226200209.GA24694@redhat.com> <email@example.com> <013a01c2e1a2$7c52fc00$485986d9@webdev>
- Reply-to: cygwin at cygwin dot com
On Mon, Mar 03, 2003 at 04:32:29PM -0000, Elfyn McBratney wrote:
>True. And I speak for the package maintainer here, of course. If there was a
>problem with one of the package files that had not already been discovered
>it would be nice to let him (me) know about it, if it hadn't already been
>reported on the cygwin-apps mailing list during the testing phase.
I don't want to beat this to death but I get the strong feeling that my
point is being lost here.
If someone can't figure out how to install a "prerelease" version of a package
then I don't think their feedback will be all that useful. Life is full of
tradeoffs. In this project, the tradeoff that I am enforcing is that we
don't clutter the list with "I can't figure out how to install the bushwah
package. How do I plug it into setup.exe so that I can install it?" email.
Of course I understand that there is a potential of missing feedback on
package installation problems but that is what cygwin-apps and the dedicated
group of people doing package review is for. Adding a secondary group of
more clueless testers is not how I want things to be handled. The cygwin
mailing list is consistently the first or second most active list on
sources.redhat.com. When I see trends developing that would tend to
increase traffic for little gain, I will take steps to stop them.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html