Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 22 May 2002 16:22:28 -0400
From: Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Adding col to cygutils
Message-ID: <20020522202228.GA19052@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020522190201 DOT 71397 DOT qmail AT web20802 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020522190201.71397.qmail@web20802.mail.yahoo.com>
User-Agent: Mutt/1.3.23.1i

On Wed, May 22, 2002 at 12:02:01PM -0700, David A. Willis wrote:
>On Wed, May 22, 2002 at 13:10:11 -0400, Christopher
>Faylor wrote:
>>Why are you contributing to cygutils rather than cygwin itself
>
>As I stated in my original message, the reason I though col belonged in
>cygutils rather than it's own package for cygwin is that other BSD
>utilities, such as cal, were already a part of cygutils.

I guess past use is normally a good justification.  However, it seems
like cygutils is a rather eclectic combination of utilities so basing
a decision to put something in cygutils based on what is already there
may not be a good plan.

I do agree that this utility belongs in cygutils, fwiw.

>From that organization I came to the conclusion that cygutils would be
>the logical location for other utilities found as part of bsdmainutils.

Fair enough.  This is a clarification of what you said in your original
message.  Thanks.

>>Well, of course.  Why would you want to send a large attachment to the
>>thousands of people reading this list?
>
>Because that is what is asked in the HOW-TO-CONTRIBUTE document that is
>part of cygutils.  It asks to send a changelog as part of the message
>text, and a patch generated via "cvs diff" along with a tarball of new
>files to cygwin AT cygwin DOT com.  If that is no longer the case, then I will
>be glad to update the HOW-TO-CONTRIBUTE document to reflect the current
>policies regarding submissions.  I would just need to know what they
>are first.

I wasn't aware that the HOW-TO-CONTRIBUTE suggested sending a tar file
to the cygwin mailing list.  That is a big no-no.  Sending binaries here
should really be a last resort type of thing.  There is no reason that
everyone on the list should be interested in seeing this type of file.

I guess I should go educate myself on the documentation that comes with
cygutils.

Maybe a clearer statement of what makes a good cygutils package would be
nice.  Why should a package be included in cygutils?  IMO, it is because
it is a small (one or two c files) general-purpose program.  The
justification that it is in the utils-linux package on Red Hat is a good
one, too.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/