Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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: Sun, 10 Apr 2005 13:28:46 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin-apps AT cygwin DOT com
To: Hans Horn <hannes AT 2horns DOT com>, cygwin-apps AT cygwin DOT com
cc: cygwin AT cygwin DOT com
Subject: Re: maintaining bash
In-Reply-To: <d3bmoq$ji3$1@sea.gmane.org>
Message-ID: <Pine.GSO.4.61.0504101318540.21111@slinky.cs.nyu.edu>
References: <423AE723 DOT 3090801 AT buddydog DOT org> <6 DOT 1 DOT 2 DOT 0 DOT 0 DOT 20050318073557 DOT 01f85cc0 AT imap DOT myrealbox DOT com> <d348aa$6r6$1 AT sea DOT gmane DOT org> <4255B3C7 DOT 9030306 AT buddydog DOT org> <4255B8AC DOT 2C88CDE6 AT dessent DOT net> <d34i0v$hdk$1 AT sea DOT gmane DOT org> <20050408022027 DOT GB10856 AT trixie DOT casa DOT cgf DOT cx> <d3bmoq$ji3$1 AT sea DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Sun, 10 Apr 2005, Hans Horn wrote:

> Folks,
>
> > If you are still willing then you've got the job.
> Alright, I'm on - despite a rough start!

Hans, if you plan to maintain a package, you really ought to subscribe to
the cygwin-apps list.  Packaging discussions should take place there.
I'm sending my reply there as well, and setting Reply-To: appropriately.

If you don't want to actually receive cygwin-apps messages, but want to be
able to post, you can subscribe to cygwin-apps-allow instead (see
<http://cygwin.com/ml/lists.html#rbl-sucks>).

> > There is one potential problem in that we may need to adapt Pierre's
> > patch to prevent problems with pid reuse to 3.0 if it is released.
> How do I go about Pierre's pid patch?

You'll need to see exactly what it changes in the 2.05 sources, find and
modify the corresponding places in the 3.0 sources, and then (the hardest
part) test that the fix actually works.

> > The next step is to create a package and offer it on the cygwin-apps
> > mailing list.
> > Please look at the archives for examples of how this is done.
> I'm a total virgin at this. I'm afraid I need help, professional help!

WHAT?!  Do you know how much those people CHARGE?! ;-)

> Right now I'm looking at http://cygwin.com/setup.html, as well as what
> ships with the binary and source distribution of the current cygwin
> bash.  Looks like bash2.x install in /usr/bin while bash3.x installs in
> /usr/local/bin.  Is that ok?

No, it isn't.  Cygwin programs get installed in /usr/bin.  If the upstream
package doesn't go there by default, you'll need to patch the sources in
such a way that the files do get installed there.

> As to Andrew Schulman's complaint about the "extra-space-after-the-prompt"
> bug (http://sources.redhat.com/ml/cygwin/2005-04/msg00325.html, first
> reported at http://mail-index.netbsd.org/pkgsrc-bugs/2005/03/25/0002.html),
> I believe to have fixed the problem. How do I about getting this fix (if we
> conclude that it is indeed working) back into mainstream bash?

You generate a patch (using "diff -puN" against the original sources),
make sure that the patch contains only the fix for the above problem, and
then submit the patch to the upstream batch distribution using the means
no doubt documented on the bash homepage.
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"The Sun will pass between the Earth and the Moon tonight for a total
Lunar eclipse..." -- WCBS Radio Newsbrief, Oct 27 2004, 12:01 pm EDT

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/