Message: previous - next
Month: April 2012

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

From: Julius Schwartzenberg <julius.schwartzenberg@...>
Date: Sat, 28 Apr 2012 15:52:13 +0200
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.

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?

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?

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.

Best regards,