On Friday 18 January 2008 01:08:51 Neil Bothwick wrote: > > Actually it was decided to keep monolithics in KDE 4.0.0. Splits are > > now the default which means they are listed first in any-of dependency > > blocks such as e.g. || ( kde-base/kompare:kde-4 kde-base/kdesdk:kde-4 ) > > in KDE 4. But monos are still around. There is a list of the monos in > > the url I posted in another mail to this thread. > > Would it be possible to modify the kde-meta eclass so that a split vs > monolithic block gave a more informative error message. Even a generic > message pointing to that URI would be a great help.
Since we only have the RDEPEND="!kde-base/kdesdk:kde-4" etc. dependency syntax which doesn't allow messages I don't see how (if you see a possibility I'm missing say so). The message you get is a generic resolver failure. If you have ideas for better wording of the blocker message from portage I guess you should file a portage bug. If you have any ideas for extending the ebuild format to make it possible to add custom messages with urls then I guess filing a PMS/EAPI bug is the way to go. -- Bo Andresen
signature.asc
Description: This is a digitally signed message part.
