Re: Python or Perl for a Debian maintainance project?
Andrew Suffield <firstname.lastname@example.org> wrote:
> And yet in the real world, it's the kind that gets left unfixed, while
> the latter kind does not. Resulting in a lot of code that crashes and
> burns for things that really didn't matter. I'd rather have a daemon
> silently ignore an error than die for a non-error.
By the way, why you think Policy § 6.1 so strongly recommends the use of
"set -e" in maintainer scripts?
| 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).
This is precisely defeating your ridiculous statement.