|
Home > Archive > Debian Developers > December 2006 > Template toolkit: removed functionality issue
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Template toolkit: removed functionality issue
|
|
| Dominic Hargreaves 2006-12-23, 1:35 am |
| Hello,
I write as someone preparing an NMU for
http://bugs.debian.org/cgi-bin/bugr...cgi?bug=393311.
Template Toolkit 2.15 removed a few plugin modules from the main
distribution and I would like to package this new version.
The plugins removed are:
Template::Plugin::DBI
Template::Plugin::XML
Template::Plugin::GD
I've checked packages depending on libtemplate-perl, and the only
package that appears to use any of these plugin modules is bugzilla.
Would it therefore be okay to simply package libtemplate-plugin-gd-perl,
and have bugzilla depend on it (and possibly the equivalent
libtemplate-plugin-dbi-perl and libtemplate-plugin-gd-perl packages),
and then upload a new libtemplate-perl reflecting upstream's changes
with a NEWS.Debian entry explaining the change? Should libtemplate-perl
then Recommend or Depend on the new separate plugin modules? My
intuition would be to avoid a Depends.
Thanks,
Dominic.
--
Dominic Hargreaves | http://www.larted.org.uk/~dom/
PGP key 5178E2A5 from the.earth.li (keyserver,web,email)
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Benj. Mako Hill 2006-12-24, 1:39 am |
| <quote who="Dominic Hargreaves" date="Fri, Dec 22, 2006 at 04:47:10PM +0000">
> I write as someone preparing an NMU for
> http://bugs.debian.org/cgi-bin/bugr...cgi?bug=393311.
>
> Template Toolkit 2.15 removed a few plugin modules from the main
> distribution and I would like to package this new version.
> The plugins removed are:
>
> Template::Plugin::DBI
> Template::Plugin::XML
> Template::Plugin::GD
>
> I've checked packages depending on libtemplate-perl, and the only
> package that appears to use any of these plugin modules is bugzilla.
> Would it therefore be okay to simply package libtemplate-plugin-gd-perl,
> and have bugzilla depend on it (and possibly the equivalent
> libtemplate-plugin-dbi-perl and libtemplate-plugin-gd-perl packages),
> and then upload a new libtemplate-perl reflecting upstream's changes
> with a NEWS.Debian entry explaining the change? Should libtemplate-perl
> then Recommend or Depend on the new separate plugin modules? My
> intuition would be to avoid a Depends.
If Bugzilla can be updated to include a depends on the new package, it
should be turned into a recommends.
Later,
Mako
--
Benjamin Mako Hill
mako@debian.org
http://mako.cc/
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|