On Tue, May 20, 2008 at 09:02:25AM +0200, Jonas Smedegaard wrote: > On Tue, May 20, 2008 at 01:42:55AM -0400, Rene Mayorga wrote: > > > >> Either we just admit that the package has changed, and warn about > >> that in debian/NEWS. > > > >Sounds nice for me, but I also think that we should add the notice in > >POD and html2wiki to catch more despite users :). > > Good idea. Feel free to add patches, and get in touch with upstream > suggesting them to adopt those patches.
Actually I missed that html2wiki binary pokes the user about this change (yes, I was one despite user too :)) So I'm only adding a note to HTML::WikiConverter POD noting this change. Also I add the debian/NEWS file > > >> Or we make the main package depend on the submodules formerly part of > >> the module. > > > >Having a dep on all the submodules will came to have a bunch of modules > >installed, this also will follow to have the need to add a depend to > >every -dialect module that could be added to the archive. > > Not all of them - that's what the virtual package is for. Just the ones > formerly part of the main module. > > And if we choose that apporach, then yes, other users not needing those > submodules are forced to install them anyway. We can drop the > dependencies after lenny+1 is released as stable. Ack, and at this moment this is not a big issue the only packages available are -wikiconverter-markdown and -wikiconverter-moinmoin and the -wikiconverter-mediawiki ITP This will not load too much considering that the previous package contains this modules and several more > Alternatively we can rename the main package to -core, replacing it with > an empty transitional package hard-depending on -core and the used-to-be > submodules. that would avoid surprises for old users and also support > new users uninterested in the added dependencies. But I believe it > would violate Debian Perl Policy (main module is not called -core). Yes, renaming to -core will conflicts with Debian Perl Policy naming convention > I favor a combination of first and second option: > > 1) Document that content of main module has changed > 2) Have main module recommend formerly included submodules Just for made this point clear, you suggest a Recommend directly to all formerly submodules or you suggest keeping the Recommends to the virtual packages provides but the submodules? > 3) Drop explicit submodule-recommendations after lenny+1 > Cheers. -- Rene Mauricio Mayorga | jabber: [EMAIL PROTECTED] http://rmayorga.org | -------------------------------------------------- 08B6 58AB A691 DD56 C30B 8D37 8040 19FA A209 C305
signature.asc
Description: Digital signature