Le Sun, Feb 26, 2012 at 04:39:59PM -0800, Russ Allbery a écrit : > > I thought about this more this morning, and realized that the real > solution to all of this is to make the upgrading checklist an appendix to > Policy. That way, we can use regular internal document links and let the > documentation build system resolve them and turn them into appropriate > links, and the upgrading checklist would naturally come as part of the > overall Policy document in every format. > > However, I'd rather not do that work in DebianDoc-SGML (see the upcoming > long-term strategy message that I'll write later today). It feels better > as part of a more thorough overhaul when we're changing things around > anyway.
Hi Russ, I had similar thoughts when preparing the patch, but did not propose the merge as I did not find an easy way to produce with DebianDoc-SGML a stand-alone text version of the upgrade checklist, which I think has some value. My gut feeling is that it may be doable with DocBook XML, so it is a good idea to postpone invasive changes to the conversion. Have a nice day, -- Charles -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120227020553.ga24...@falafel.plessy.net
