LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Bug hunting in -current [a minor issue to me...] (http://www.linuxquestions.org/questions/slackware-14/bug-hunting-in-current-%5Ba-minor-issue-to-me-%5D-539687/)

truthfatal 03-22-2007 12:56 PM

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).

nymusicman 03-23-2007 03:38 AM

I'm sorry this doesn't answer your question but where did you find the slack build for compiz?

titopoquito 03-23-2007 05:07 AM

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.

XGizzmo 03-23-2007 03:02 PM

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.

truthfatal 03-23-2007 04:25 PM

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).

erklaerbaer 03-25-2007 07:36 PM

actually kde is enabled.

Quote:

CFLAGS=$SLKCFLAGS \
CXXFLAGS=$SLKCFLAGS \
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--infodir=/usr/info \
--mandir=/usr/man \
--disable-static \
--disable-gconf \
--enable-kde \
--enable-librsvg \
--build=$ARCH-slackware-linux
i'm building compiz right now.

IMHO this deserves some attention; compiz is at least as much important as the libc ;)

truthfatal 03-25-2007 07:56 PM

Quote:

actually kde is enabled.
I know, the problem is that even though the default package is built with KDE enabled, it doesn't include kde-window-decorator, which is required for compiz to work on KDE. I just want to know where/when/why kde-window-decorator disappeared from the original package, because building my own package using the exact same configure --flags does build and properly include kde-window-decorator.

Quote:

compiz is at least as much important as the libc
I know! :D


All times are GMT -5. The time now is 04:52 PM.