Hi, Lars Wirzenius wrote:
> Updating the patch should, I think, be done > only after the draft is final and policy is ready to include it in the > package (even if only in the policy VCS repository). If you mean that there is no need to update to an intermediate version, makes sense to me. Anyway, getting any version ready to include in the VCS (on a branch) seems worthwhile to me, and after that, updating should be easy. Caveat: I am only guessing (and faintly remembering some discussion) about what formats are acceptable. I just started working through policy bugs a couple of days ago. So please do not trust me. :) > Converting the DEP5 > draft to whatever format is acceptable to policy should be fairly quick, > only an evening's work or so. DEP5 should not require anything much in > the form of markup, except tables (not sure if debiandoc supports > tables). debiandoc does not support tables. That's one of many reasons policy should eventually move away from it. Maybe a <taglist> can work for the list of licenses in the short term? > Having DEP5 wait for some docbook work in the debian-policy package > would be unfortunate. I can try this weekend to write some makefile rules to build from docbook XML. IMHO it would not be worth it to couple this with converting policy.sgml itself. Thanks, Jonathan -- 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/20110302093322.GB14737@elie
