Bug hunting in -current [a minor issue to me...]
For some reason the compiz that comes in -current doesn't include `kde-window-manager` executable script.
I've re-compiled the program (same tarball from src/ dir) using the exact same configure flags as in Slacks build script and I do get the kde-window-manager script. I'm in fact using compiz right now, rather than beryl.. (I wanted to see if I could get the composite WM that is included to work, because I don't have anything better to do, so I might as well test too see what works in -current) So, I've grep'ed my way through all of the slackware x/ and kde/ build scripts in -current. there is no mention of "kde-window-manager" in any of them (let alone removing it), and I am now wondering if anyone can point me in the right direction to find out where the differences are? Where did the file go in Slackwares build? Weird. I imagine this could be a bug, but I don't want to bug any Slack Devs with it until I know the what/where/why of the problem... Maybe I just had a bad package... re-checking md5sums as I type (dang! none failed). |
I'm sorry this doesn't answer your question but where did you find the slack build for compiz?
|
ftp://slackware.cs.utah.edu/pub/slac.../source/x/x11/ -- you have to look through the folders, some have files for compiz some not (e. g. doinst.sh).
You can always look in the source folder to grab the original Slackbuild script. |
kde support in compiz has to be enabled. It is disabled by default. I doubt it will be enabled on slackware since that would create a kde dependency in compiz.
|
Like I said, it's only a minor issue, however, I don't see the point in including compiz if it's not going to work on any of slacks DEs (It's not built with gtk support either).
|
actually kde is enabled.
Quote:
IMHO this deserves some attention; compiz is at least as much important as the libc ;) |
Quote:
Quote:
|
All times are GMT -5. The time now is 10:02 AM. |