Re: Template toolkit: removed functionality issue
> 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 > 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 [EMAIL PROTECTED] http://mako.cc/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Template toolkit: removed functionality issue
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. User-installed packages do not matter, they are at risk of breaking anyway after every upgrade. -- ciao, Marco signature.asc Description: Digital signature
Re: Template toolkit: removed functionality issue
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 the new separate plugin modules? My > > intuition would be to avoid a Depends. > > Potentially breaking working webapps is not a nice thing, though. > 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 > kind of suprises and should be conservative and diskspace is > cheap. You can change the depends to a recommends for lanny (or > was it larry? lenny?) later on. Really the question boils down to what sort of guarantees we are providing to people using these libraries *not* via a package in the Debian archive, though. I've already demonstrated that it is easy to simply have bugzilla add a dependency, and my thought is that anyone using the functionality not as part of a package would have had the same upgrade issue had they been installing Template Toolkit from the vanilla CPAN sources. There's only so far we can go to support software that we don't know about. I'm not arguing hard for either route, though. Cheers, Dominic. -- Dominic Hargreaves | http://www.larted.org.uk/~dom/ PGP key 5178E2A5 from the.earth.li (keyserver,web,email) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Template toolkit: removed functionality issue
* 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 Depends. Potentially breaking working webapps is not a nice thing, though. 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 kind of suprises and should be conservative and diskspace is cheap. You can change the depends to a recommends for lanny (or was it larry? lenny?) later on. /andreas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
