Clint Adams wrote: > That's 688 packages in violation. It makes 'set -e'
unusable in #!/bin/sh scripts. That's 6810 packages in violation. At least 7498 packages in sid have preinsts, prerms, postinsts, or postrms which violate Debian policy.
Put the crackpipe down, and read:"The package management system looks at the exit status from these scripts. It is important that they exit with a non-zero status if there is an error, so that the package management system can stop its processing. For shell scripts this means that you almost always need to use set -e (this is usually true when writing shell scripts, in fact). It is also important, of course, that they don't exit with a non-zero status if everything went well."
Fix the shells, not the policy. If somethign can't handle "set -e", fix it. Is thats what is going on here?
If your on some crusade to forego common sense and choose the easiest way out, follow Manoj's suggestion to find another hobby.
-- Scott Dier <dieman@ringworld.org> http://www.ringworld.org/ -- To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org