Hi Chris, on Friday, 2006-07-28 at 09:41:09, you wrote: > Well, we would hope that people using the package would file a bug, but > this obviously doesn't always happen.
Even if it happens that doesn't mean anything is gonna change :)
I'd like to get involved and help out with stuff like this but frankly I
don't know where to start ATM.
The thing is, I maintain net-misc/hsc, upstream that is. The latest
stable version in portage is two years old, the unstable one is almost
1yo and buggy. Now there's been a fix for about 5 months now, even comes
with an ebuild, maybe not a very good one but it works on various platforms.
I notified the developer that made the last ChangeLog entry in March,
and again in June, copied to some others devs from the log when there was
no reply, opened a bug (#140242) some two weeks ago---still nothing.
Seems I'm not following some arcane protocol. I mean, I'd be fine with
any comment.
"Your ebuild sucks, read $DOC and fix it"---Cool.
"We don't have time for the three-and-a-half users of this package, just
submit it for an overlay at $FOO"---Fine, I know what to do.
"Mail $DEV and see to it that you get dev status yourself"---OK.
Hum. Well, I've been subscribed here for a while to get a feeling for
the dev process, and this seemed like a good opportunity. Maybe someone
else can tell me where to start?
cheers!
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
pgpUA1DhAtkLp.pgp
Description: PGP signature
