On Thu, 12 Feb 2009, Colin Watson wrote: > > In the long term, I would like to move all the documentation about the > > syntax into dpkg itself and have the policy document how Debian uses > > dpkg rather than documenting dpkg itself. > > The mythical dpkg programmer's manual? :-)
We do have quite a lot of documentation in dpkg already. All tools are extensively documented. Only file formats are not well covered. But we do have: deb-substvars(5), deb-shlibs(5), deb-triggers(5), deb-control(5), deb-version(5), deb(5), deb-override(5) and deb-symbols(5). We need deb-changes(5), deb-dsc(5) and deb-src-control(5). > I was never all that convinced. I do think there's value in the policy > manual being coherent in itself, rather than depending on another manual > for all the syntax. (I realise you already need to learn make and It depends, and there can be some repetition when needed to ease the comprehension. But you don't need to know the .changes syntax to create policy conformant packages, you just have to know how to call dpgk-genchanges and what to put in debian/files and debian/changelog and debian/control. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org