[Third try. Maybe the attachment's too big? I'll compress it.] Chapter 4, required files. I'm making this chapter harder for myself by trying to harmonise its use of jargon with Policy. For a start in 4.1 there's the subtle difference between "control files" (meaning the ones named "control") and "control files" (.dsc files are also control files); though in this case we're safe thanks to DocBook's <filename> tags. In the following couple of paragraphs I have changed a couple of things: "section" and "subsection" become "(archive) area" and "section". I've also taken out a reference to the abolished "base" section (and standardised on hyphenless "email"). It's possible that the explanation in 4.1 about the Architecture line of the control file needs to be updated, now that architecture can mean "kernel" as well as "broad CPU-type category". The description of Suggests claimed that "all frontends will likely prompt [users] to install" the suggested packages (the same phrase as for Recommends), before going on to admit that it's false for dpkg, apt-get, and almost always aptitude. I've made it more accurate by reversing it to say they probably *won't* do this. I've done a couple of package description spelling fixes (s/a object-oriented/an object-oriented/ and s/utilises/utilizes/ to match earlier "customizing") in the example debian/control file at the end of 4.1; I'd better send in a corresponding wishlist bugreport for the real gentoo package description. [PS: done, #623855] 4.4.1 ends by recommending "info make". Unfortunately these days that's in the non-free package make-doc. -- JBR with qualifications in linguistics, experience as a Debian sysadmin, and probably no clue about this particular package
Attachment:
ch4a.diff.gz
Description: Binary data