Releasing a module with additional dependencies

[Joel Bernstein]

Yes. Make it a mandatory dependency. Or if the new dependency is enormous,
difficult to install, will not be used by 95% of your module's users then
put the new functionality into a separate distribution which depends on
your current one. But I expect if you could've more sensibly used a new
distribution you'd've done that already.

/joel


On 15 April 2014 15:39, Leo Lapworth <leo at cuckoo.org> wrote:

> Make is a mandatory dependency.
>
> This is what every other CPAN module does and is easiest for your module
> users.
>
> Leo
>
>
> On 15 April 2014 15:27, Andrew Beverley <andy at andybev.com> wrote:
>
> > Hi guys,
> >
> > A bit of a newbie question on publishing a module.
> >
> > I've just taken over as maintainer of Device::VantagePro and released a
> > new version with some additional features. One of the features
> > (get_timezone) requires DateTime::TimeZone, which was not previously
> > needed.
> >
> > I need some advice as to whether I should:
> >
> > 1. Make DateTime::TimeZone a new mandatory dependency for the whole
> > module, even though people might not need the functionality that relies
> > on it. This is my preference, but is that approach considered to be a
> > Bad Thing?
> >
> > 2. Add DateTime::Timezone as an optional dependency. In this case could
> > someone please point me in the direction of instructions on how to do
> > this (Google is failing me).
> >
> > Currently the module is failing build tests as I have not implemented
> > either of these options.
> >
> > Thanks,
> >
> > Andy
> >
> >
> >
>
>