quote who=Dominic Hargreaves date=Fri, Dec 22, 2006 at 04:47:10PM +
I write as someone preparing an NMU for
http://bugs.debian.org/cgi-bin/bugreport.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.
Hello,
I write as someone preparing an NMU for
http://bugs.debian.org/cgi-bin/bugreport.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
* Dominic Hargreaves ([EMAIL PROTECTED]) [061222 17:47]:
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
On Fri, Dec 22, 2006 at 08:06:00PM +0100, Andreas Schuldei wrote:
* Dominic Hargreaves ([EMAIL PROTECTED]) [061222 17:47]:
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
On Dec 22, Andreas Schuldei [EMAIL PROTECTED] wrote:
The conservative thing to do would be to depend on the new plugin
modules. I think debian is trying to protect the user from these
While the smart thing to do would be to add a versioned conflict with
the packages which would be broken.
5 matches
Mail list logo