Colin Watson wrote:
>> Looking into the code, the reason is in src/configure.c where a
>> putchar('\n'); is done when maintainer_script_installed() returns !=
>> 0. Maybe someone wanted to make sure that after execution of
>> maintainer scripts, a proper CR is done? On the other hand side, all
>> the other invocations of maintainer_script_installed() (including the
>> "post-installation" ones like the above one) don't handle it that way.
>
> I always thought this was useful information; it made it easy to see in
> upgrade logs from users when a postinst script was being run (and while
> it was a bit inconsistent, postinst scripts are usually the most
> interesting case so this was OK).
>
> Would you please reconsider this and reinstate the blank line when a
> postinst is run?
The original reason why I filed the bug is that (if you don't know
what's going on / postinst runs) it looks quiet "untidy" in the protocol
output if there are sometimes empty lines and sometimes not.
Alternatives that come to mind to address your concern:
* Print "Processing postinst" instead of new line
* Print "Setting up ..." only for packages where the maintainer script
is run.
Thanks for considering.
bye,
Roland
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
