Hear here.. I have not read all the post yet, but just enough.
Example: Installing/Compiling Gambas from source...
In MDK, its just ./configure make make install.
Bingo, everything works.
In SuSe 9.1pro however, you have to tell ./configure where
everything is and where you want it.
./configure \
--with-kde-libs=/opt/kde/libs \
--with-kde-incl=/opt/kde/incl \ << I know this is not right, just and example...
--with-blahblah about 6 more times for postgrsql, mysql, ect,ect...
Arrghgh...
Note: Gambas that comes with SuSe 9.1 Pro is broke from start, obviously was not tested
before hand.
And to top it off, you have to dig for days to find that
information.
Although Yast works pretty good, I don't see what all the fuss is
about it. I haven't had problems with anaconda or mcc on initial installs or Yast
for that matter. But Yast is terribly slow, and they all do have problems after
the initial install. Especially, Yast and MCC.
All these, although little things to us, are big things to new comers and
people that want things to work from the start. I thought thats why I bought SuSe.
Technonoid