On Thu, 5 Jan 2006 11:41:22 +0000 Neil Bothwick <[EMAIL PROTECTED]> wrote:
> If would be nice is portage had a means for developers to handle these
> types of conflicts in the ebuild. A similar thing happened recently
> with xpdf/poppler, it happened with some FTP servers and the ftp-base
> package not long ago. I realise it is not possible to handle all
> conflicts, but with some instances, like this one, the conflict is
> expected. even if there were just a means to print a message if a
> package hits a block, something like
>
> if_blocked_by('openmotif')
> ewarn "You must unmerge openmotif before proceeding"
An error message like that doesn't really tell the user anything that he
doesn't already know.
It would be more useful if some information was provided:
if blocked_by >=x11-libs/openmotif-1.2.3 ; then
eblockinfo "Due to changes with blah, it is recommended that"
eblockinfo "you foobar. See http://bugs.gentoo.org/123456.";
fi
But then, at what point would this information be echoed to the user?
It would have to be during the same pre-merge phase that the blocking
errors appear. Then again, I don't really see any gaping problems with
the current system; once someone has encountered their first pair of
blocking packages, they then understand how to fix blockers in future.
I doubt it's worth the effort.
/shrug
--
Tom Martin, http://dev.gentoo.org/~slarti
AMD64, net-mail, shell-tools, vim, recruiters
Gentoo Linux
signature.asc
Description: PGP signature
