On Monday 07 of November 2005 13:42 Paul Waring wrote:
> If it's a commonly-encountered problem with a known solution (or at
> least things you can try), why on earth wouldn't you want that in the
> documentation? If it's not there, you're going to have more users on the
> forums/IRC asking "why am I getting problem X?" (I've had circular
> dependancy problems with python in the past) and you can't exactly tell
> them to RTFM if there isn't one.
>
> It doesn't have to be in the handbook itself, a separate document would
> do, but if lots of people are experiencing similar problems it would be
> sensible, at least in my opinion, to have some sort of written
> documentation that they can look to.

You probably haven't read the whole thread.

The problem is that there are circular dependencies. This is caused by several 
packages from our tree depending on each other. We (the GDP) can't really 
provide a fix for such cases as they will randomly appear and disappear as 
the tree changes and are quite unpredictable. If an experienced user needs to 
do such an advanced install, (s)he will most probably know how to get over 
circular dependencies.

WKR,
-jkt

-- 
cd /local/pub && more beer > /dev/mouth