Originally Posted by dad_
Do you assemble slackware packages and install them or just do "make install"? Are git versions always stable? Are there compilation failures? Having a single script is of course more convenient than using a bunch of different slackbuilds from different (sometimes unknown) sources. If you compile everything yourself you don't need a binary distribution at all - you could use gentoo for example.
Yes, I do create slackware packages, I wrote Slackbuilds-like scripts for that. It's much better to make upgrades and potentially go back to a working packages if anything goes wrong.
But on the whole, I've been doing this for years and never had an unstable desktop yet. X11 and mesa packages are well developped, I almost never have compilation failure.
I actually wrote single Slackbuild for each package, and I ended writing a master script that starts the various Slackbuilds, with some error handling and logging. I guess I have some free time.
I just compile mesa drivers and some multimedia stuff, because they are fast changing, adding new features very often, but not releasing that often. For the rest of the OS, I'm quite happy with Slackware-current and alienBOB's kde and multilib packages. They're recent enough and compiling the whole thing would be tedious.
I don't think what I do is that much different to getting regularly new binary drivers. It's almost as easy since I've automated everything and not much longer.
--enabled-shared isn't required technically. It should build with the static libs.
True if you compile Mesa with "--disable-llvm-shared-libs". That's what I do. You get some warning during the compilation about that but I've never had any issue that could be tied to that. I don't do any gaming though, so I'm probably not pushing the OpenGL support to the limit.
It would be nice if Pat added shared libs to LLVM though.