Message: previous - next
Month: April 2012

Re: Re: [trinity-devel] Re: Resolving the TWin/KWin Fork Issue

From: Martin Gräßlin <mgraesslin@...>
Date: Sat, 28 Apr 2012 17:46:03 +0200
On Saturday 28 April 2012 15:52:13 Julius Schwartzenberg wrote:
> Martin Gr��lin wrote:
> > On Friday 27 April 2012 17:59:31 Julius Schwartzenberg wrote:
> >> Maybe the kwin4 developers themselves could provide a stripped-down
> >> version of kwin4 for multiple popular distributions? I would imagine
> >> starting with adding a kwin-lite package to Debian/Ubuntu which would
> >> only have the limited set of dependencies. Maybe people on other DEs
> >> would like to use this package as well.
> > 
> > KDE developers do not do packaging. We have distributions for that. We
> > only
> > provide source code and the source code can be stripped down:
> >
> > 
> > If anyone wants to have stripped down packages he has to do it. The KWin
> > developers will not do that for you, sorry. I am not so stupid to assume I
> > could make packages- I leave that to experts in packaging.
> True of course, but in this case there is a chicken and egg problem.
> The kwin4 developers would like to see kwin4 being used outside of KDE4
> and currently distribution packagers assume kwin4 is only meant to be
> part of KDE4 and package it as such.
No, distributions package for what is demand. E.g. Kubuntu is shipping in 
12.04 four versions of KWin.

As we are currently talking of a not yet released version of KWin anyway it 
does not make much sense to say there is a chicken-egg problem.
> I'm not a packaging expert either. Although I may be able to look into
> this in the future, I guess for now it would be good to create a report
> maybe on Launchpad.
> Martin, do you have a proposal for the name of this package? There seem
> to be multiple kde-window-manager* packages already on Ubuntu. Would a
> -lite suffix seem appropriate to you?
I have nothing to do with packaging. I cannot give any recommendations. That's 
up to the Ubuntu community.

But honestly I doubt that Ubuntu would include any Trinity specific version of 
KWin given that there are no other packages for Trinity available.
> With which options exactly would you compile this version? Would
> disabling *all* build options give a representable build of kwin4? There
> are some options that are not fully obvious to me. What happens when
> kwin4 wouldn't have decorations?
well the options do what they name. If you disable decorations there won't be 
decorations, quite simple :-) It's a build option used for KDE's tablet user 

So no turning all build options off doesn't make any sense.
> If there would be a short set of complete commands to fetch the source,
> configure it with limited dependencies, etc. it could also be put on the
> Trinity wiki to encourage testing.
Excerpt from my Jenkins build job to test the compile options used for Plasma 
mkdir $WORKSPACE/../build
cd $WORKSPACE/../build
cmake -
DCMAKE_PREFIX_PATH=/usr/share/tomcat7/.jenkins/jobs/kdelibs-4.8/install/ \
cd kwin
make -j3
make install

So yes it is possible to have a small script :-)