rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: Tim Goodwin <tgoodwin@cygnus.co.uk>
To: broman@nosc.mil
Cc: debian-devel@lists.debian.org, rc@hawkwind.utcs.toronto.edu
Subject: Re: "rc" shell maintainer?
Date: Thu, 5 Feb 1998 06:46:00 -0500	[thread overview]
Message-ID: <XhgAAI2m2TSjHwwA@nan.cygnus.co.uk> (raw)
In-Reply-To: <19980204212332.10457.qmail@np.nosc.mil>

> Who is maintaining the rc package for Debian GNU/Linux?

Can't help here.

>                                          There is also an
> unstable rc-1.5b2 owned by debian-qa, I think,

By "unstable", do you mean that you are aware of specific problems?  If
so, *please* let me know about them.

> The upstream package maintener seems to be Tim Goodwin,
> since last summer, but the mailing list for rc is quiescent.

Yes, it's been fairly quiet around here.  The current status of rc-1.5b2
is this.

o There is a significant problem around the wait() code, which can cause
rc to hang on (at least) Linux systems if you '^C' an application.
There is a fix for this in the development version, but I'm not entirely
happy with it yet.

o There is a different bug near wait() which I haven't had a chance to
track down yet.

o There is a major thinko in the autoconf handling of signals, which
causes problems on RedHat 5.0 (but hasn't been reported anywhere else).
I believe this will be straightforward to fix.

o Some minor tweaks and enhancements to configure have been requested.

I haven't had much time recently to spend on rc, but as you can see from
the above list, there's not much to be done before I release rc-1.5b3,
and I *hope* that will be the last beta before a full rc-1.5 release
(but maybe not :-).

Again, if you've had any problems with rc-1.5b2, whether with the
autoconfiscated build process or with the shell itself, please let me
know.

Thanks,

Tim.


  parent reply	other threads:[~1998-02-05 21:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-04 21:23 Vincent Broman
1998-02-05  1:17 ` Tom Culliton
1998-02-05 11:46 ` Tim Goodwin [this message]
1998-02-05 21:48   ` Vincent Broman
1998-02-06 18:00     ` Tim Goodwin
1998-02-06 22:54       ` Vincent Broman
1998-02-09 20:31       ` Vincent Broman
1998-02-09 23:45       ` Vincent Broman
1998-02-10 23:26         ` Tom Culliton
1998-02-11 10:45           ` Tim Goodwin
1998-02-11 22:23             ` Tom Culliton
1998-02-12 10:23               ` Tim Goodwin
1998-02-11 21:55           ` Vincent Broman
1998-02-05  5:01 smarry
1998-02-05 15:25 ` Tom Culliton
1998-02-06 17:45 ` Tim Goodwin
1998-02-05 19:59 smarry

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=XhgAAI2m2TSjHwwA@nan.cygnus.co.uk \
    --to=tgoodwin@cygnus.co.uk \
    --cc=broman@nosc.mil \
    --cc=debian-devel@lists.debian.org \
    --cc=rc@hawkwind.utcs.toronto.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).