Re: Problems with forked packages and CPAN
- From: Dominique Dumont <domi@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 31 Mar 2006 08:08:03 GMT
zendonut@xxxxxxxxx writes:
I did contact the modules' maintainer about the bugs via CPAN's RT,
even supplying patch files, but they never made the necessary
updates to their own CPAN releases, and I got tired of waiting.
(It's now been months.)
CPAN's RT is quite new (compared to CPAN) and may not be read by
modules authors.
For each module rejected by the indexer, you should mention whether
the original author rejected the patch or simply did not respond.
For the former case, you'd need to fork and rename the module. But
that would be a really bad thing if you provide only bug fixes and not
major changes.
For the latter, we'd have to check if the module are really orphan and
find new maintainers (possibly you).
HTH
--
Dominique Dumont
"Delivering successful solutions requires giving people what they
need, not what they want." Kurt Bittner
.
- References:
- Problems with forked packages and CPAN
- From: zendonut
- Problems with forked packages and CPAN
- Prev by Date: Net::OSCAR and do_one_loop question
- Next by Date: Deparse
- Previous by thread: Problems with forked packages and CPAN
- Next by thread: Net::OSCAR and do_one_loop question
- Index(es):
Relevant Pages
|
|
