Yanick Champoux wrote:
On 12-01-10 03:25 AM, Tim Bunce wrote:
I can do that, no problem. The only thing I'm afraid of, is that by
not giving a specific timeframe, human psychology will do what human
psychology does and people will tend to disregard the deprecation
notice. :-)
But you are right, there is no rush to actually remove the module
itself, and perhaps the warning alone will do its job of nudging most of
the last stragglers toward DBI.
There is another option, assuming that Oraperl is just a wrapper over
DBD::Oracle.
You could split off Oraperl into a separate CPAN distribution which depends on
DBD::Oracle. People who need Oraperl install both, and those that don't, don't.
After the first release of Oraperl in a separate distro, as long as you don't
change something in DBD::Oracle that breaks the API that Oraperl depends on, you
never have to release another version of Oraperl itself again.
Then you don't have to think about deprecation of Oraperl so much as deprecation
of DBD::Oracle features that Oraperl depends on, which is much less likely since
other things probably use those features too.
-- Darren Duncan
