From: Gary Benson <gbenson@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: Re: moving rhug packages into Red Hat Linux?
Date: Tue, 22 Jul 2003 13:25:00 -0000 [thread overview]
Message-ID: <20030722132511.GE2824@redhat.com> (raw)
In-Reply-To: <3F1D37D1.6000600@myrealbox.com>
Nicholas Wourms wrote:
> What ever happened to those rhug packages that showed up on rawhide
> for awhile during April-June? Also, what's the story with the
> gcc-ssa that was in rawhide (I assume in conjunction with the rhug
> packages)? I assume these packages are still being worked on
> internally, so any chance that they could be posted on
> people.redhat.com?
Now _that_ is a good idea. All those packages (except gcc-ssa) were
mine, repackaged RHUG packages which I've been working on internally.
I hadn't wanted them in rawhide because there are still a few big
issues with them -- my past experience has been that putting such
packages in rawhide results in a flood of 'Warg, package $foo doesn't
work on my box, Red Hat sux!!!!!' messages that waste a lot of time.
(Subscribe to rhl-beta-list@redhat.com and you'll get the message!)
But a low-publicity release on people.redhat.com might be just the
ticket. I'll let you know how I get on.
> Also, why were the gcj Sun compatibility wrappers axed from severn?
> I can't speak for everyone, but I found them quite useful. They
> also seemed to be a very low-maintenance package.
What, you mean gcj-jdk or whatever it was called? There were issues
with it that nobody had the time or inclination to resolve, so they
were dropped.
Cheers,
Gary
[ gbenson@redhat.com ][ GnuPG 85A8F78B ][ http://inauspicious.org/ ]
next prev parent reply other threads:[~2003-07-22 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-21 19:57 Per Bothner
2003-07-21 22:57 ` Tom Tromey
2003-07-22 13:11 ` Nicholas Wourms
2003-07-22 13:25 ` Gary Benson [this message]
2003-08-04 15:19 ` Gary Benson
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=20030722132511.GE2824@redhat.com \
--to=gbenson@redhat.com \
--cc=rhug-rhats@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).