Le jeudi 13 août 2009 00:48:13, Manoj Srivastava a écrit : > > That makes a difference in the sense that it helps to improve the > > workflow by putting as much information as possible in the same place. > > Oh, for Pete's sake, just run zless on the file lintian already > reports for you. If people are too lazy to run zless <file>, I kinda > doubt they are actually going to the effort of actually doing a good > job on their packages. You realize you still have to read the sections > mentioned in the policy document, right?
Treating people to be lazy will not lead to a better quality of their packages. Simplifying their work, however, will. > > Even more, if, as I suggested, it lists only changes that couldn't be > > automatised, that would make lintian a consistent tool for checking a > > package against the current policy. > > ANd how is lintian supposed to know this? Or are you saying we > have a new version of lintian every time that policy is updated, and it > hard codes the line in the upgrading checklist to report, and only > reports sections that have changes not fully checked by lintian -- and > for what? so that someone does not have to type zless <file>? I realize this is not easy to implement. I will, however propose something showing the whole list of changes. Romain -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
