Re: mucking with dpkg control files in maintainer scripts?
Frank Küster writes ("Re: mucking with dpkg control files in maintainer scripts?"):
> In other words, "commits" to the dpkg database are atomic, and if dpkg
> is called from a script started by dpkg, it will report all packages in
> the correct, current and maybe partial state, including the package
> processed so far?
Yes, exactly. (You only get to inspect the state, not modify it, for
But: if you find yourself doing this you're probably doing something