3 ms·
On most build systems, it's enough to change a default in one place, and not the same default in two different places.
by txutxu 13y ago
On most build systems, it's enough to change a default in one place, and not the same default in two different places.
- VLM 13y ago4 locations, if you count the commit. 1 place actually changes it, the rest are documentation. /debian/changelog is a highly formalized free form-ish text file explaining what changed since the last .deb package. You could put lorem ipsum in there and the package wouldn't care although it would annoy people. /debian/control is a list of recommends (why not a "depend"?) I believe this is a cosmetic change only ( 1 or 0 or 0 or 0 logically equals the result of 0 or 1 or 0 or 0, that type of thing ) (whoops edited to note that its some tasksel thing so its more than cosmetic, but for joe average doin all the defaults what matters will be the template file...) /debian/templates is the sort of free form yet structured debconf question file that actually does the task selection.
- claudius 13y agoNote that default dependency takes the first hit, i.e. A or B selects A by default, whereas B or A selects B, so the ordering in the control file does matter.