[paludis-user] --continue-on-failure tweaks?

[David Danier]

As trac needs registration (which is not possible) and paludis-sekrit
needs approval to subscribe I will post this here, hope someone will
read it.

I found two things that could be improved when using
--continue-on-failure (set to if-independent here, did not test
if-satisfied).

1. elog-demo-hook:
As the hook stated in its comments it should be put into the
(un)install_fail-directory. If done so it is called when one of the
packages in the list fails, which means during the build-process. Most
of the time this erases the elog-temp-file and with it the information
the elog-hook should provide _after_ paludis is finished. So log-entries
get lost.
I don't know if putting the script into (un)install_all_post would be
enough in all cases (--continue-on-failure if-fetch-only?), but if this
hooks are called afterwards (even if an package failed) case I don't see
any reason to keep the script in (un)install_fail. Perhaps the comments
in the script can be updated to avoid confusing new users?
If (un)install_all_post is not called when one out of many packages
fails it probably should be (the hook-name does not say anything about
success of the (un)install anyway). Or some hook could be introduced to
handle this special case.

2. information about news-items and configuration-files:
If paludis finishes successful it displays information like this:
--------8<----------------------------------------------------------
 * Checking whether the GNU info directory needs updating...
 * No updates needed

 * No unread news items found

 * Searching for configuration files requiring action...
 * Found 12 files in /etc
 * Found files in 1 directories
 * Your action is required
---------------------------------------------------------->8--------
Now if --continue-on-failure is active paludis will only display that
some packages failed and the resume-command. As most of the time only
minor packages fail, that might be written by the user (on my machine
most of the time my ebuilds fail, not ebuilds out of the portage-tree),
I think this information should be displayed even if some packages
failed. Perhaps even when --continue-on-failure is not used, as the
packages already installed until reaching the broken ebuild might have
provided updated config-files and as paludis merges packages in the
right order all these packages should be able to run using the new
configuration.
Anyway it would save me some headache after I fixed my ebuilds next time
they get broken. Now I have to update tons of configs. ;-)

Greetings, David Danier