There is no difference in a package whether it is installed as a Dependency or not really.
In Sysinstall when you select an item, it marks it to be installed with and X and auto-magically marks the dependencies to be installed with a D. The only difference is visual. The ones with an X you selected, and the ones with a D were auto-magically selected for you.
As far as I know, KDE4 won't run without Xorg, so I expected Xorg to be selected with a D when I selected KDE4; however, this was not the case.
This is no big deal, I just launched Sysinstall again and selected Xorg.
Oh, and it is possible that rajasekhar didn't like the RTM response, even though I think that SirDice did it better than most. Some just say RTM. But SirDice took the time to not just say RTM, but also to link to the appropriate sections of the Handbook.
I have seen that there are two types of documentation.
1. Step-by-step walk-thrus: These usually show the minimal required steps to accomplish a task and maybe a few optional steps as well. However, walk-thrus are poor at providing the technical information on why something should be done.
2. Technical data documentation that discusses the possibilities. It is excellent resource documentation. But poor at listing required steps.
The first type is newbie friendly and will get a newbie to a workable point, which builds their confidence. However, it will only get a user so far but it will get them to a working level.
The second documentation type, technical data, is required to further your understanding of why you did the steps in the walk-thru and to determine if there were other options you could have chosen and to take the product to new levels.
If anybody has experience as a Technical Trainer, or even just receiving professional training on a software/hardware product, you will notice that their are usually two sets of books, a Training Manual and a lab guide. Though sometimes the lab guides are just walk-thur sections at the end of a manual. The training manual is the technical data, the lab guide contains walk-thrus. This is not by accident. Most people learn better by doing than by reading.
I think the handbook is excellent documentation. While there is both types of the above documentation in the Handbook, it is more heavy on the technical data and it doesn't come close to have near enough "Walk-thru" type docs. That is why I started posting my walk-thrus on my blog, and why there is also walk-thru sites like
http://www.bsdguides.org.
A "walk-thru" is probably what rajasekhar needed, especially given that he has 3 posts (which doesn't mean he is a newbie but makes it likely).
We may have lost a potential user because we weren't "friendly" enough to him.
Did I really just ramble in text for this long...I got kinda soap-boxy...sorry.
