On Wed, Jul 9, 2008 at 5:53 AM, gregor herrmann <[EMAIL PROTECTED]> wrote: > On Tue, 08 Jul 2008 20:47:48 +0200, Ralf Treinen wrote: > Possible solutions include: > * make libcgi-pm-perl conflict (and maybe provide) with > libcgi-fast-perl; that would mean changing the Priority to extra > (also of depending packages)
..or changing the priority of the libcgi-fast-perl to optional. > * remove Fast.pm from libcgi-pm-perl and depend on libcgi-fast-perl; > that's happening right at the moment a few hundred kilometers to > the south east from, and maybe the newer package will already be > uploaded before this mail is finished :) Neat. For the short term, this seems a simple fix. > * in the long run it might be an idea to stop building > libcgi-fast-perl from the perl source package, add Fast.pm to > libcgi-pm-perl again, and create a dummy transitional package with > the usual conflicts/provides/replaces dance for libcgi-fast-perl > from the libcgi-pm-perl source package; Brendan and Niko, what do > you think about this idea? For 5.10, I moved the module to the vendor directory which on reflection was probably a bad idea (debian/rules:233-236). I'd say that the simplest solution would be to just reverse that decision, which would allow libcgi-pm-perl to provide a newer version without the path conflict. --bod -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
