in reply to Re^2: Upgrade-proofing overridden subroutines
in thread Upgrade-proofing overridden subroutines
There is an important issue which goes beyond Ovid's elegant solution. There should be a way to take over deceased modules. Text::CSV comes to mind. Is there any group who would be willing to arbitrate here? -- I would propose that a module could only be taken if the original developer does not reply for a certain period, say three months or six months. Is this a runner or are there insuperable copyright issues?
--
Anthony Staines
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Taking over broken subroutines??
by adamk (Chaplain) on Aug 16, 2006 at 14:13 UTC |
In Section
Seekers of Perl Wisdom