On Tuesday 26 November 2013 12:23:18 Maximiliano Curia wrote:
> In article <25673324.XNmJUoyzAe@martin-desktop> you wrote:
> > in todays hangout Alex asked whether kwin binary is going to be renamed to
> > kwin5 to make it possible to co-install plasma 1 and plasma 2.
> >
> > My opinion of that is
On Tuesday, November 26, 2013 12:23:18 Maximiliano Curia wrote:
> In article <25673324.XNmJUoyzAe@martin-desktop> you wrote:
> > in todays hangout Alex asked whether kwin binary is going to be renamed to
> > kwin5 to make it possible to co-install plasma 1 and plasma 2.
> >
> > My opinion of that
In article <25673324.XNmJUoyzAe@martin-desktop> you wrote:
> in todays hangout Alex asked whether kwin binary is going to be renamed to
> kwin5 to make it possible to co-install plasma 1 and plasma 2.
> My opinion of that is, that we don't need to have things co-installable.
> After
> all kde-wo
I've been working on this assumption when making the coinstallability
wiki page, I can't see any advantage is making the workspace
co-installable.
https://community.kde.org/Frameworks/Coinstallability
Jonathan
___
Plasma-devel mailing list
Plasma-devel
On Monday 25 November 2013, Martin Gräßlin wrote:
> If a distribution wants to provide Plasma1 and Plasma2 at the same time,
> they can just install them to different prefixes like how project neon
> does it. The time span when users might want to co-install Plasma 1 and 2
> is very short. Maybe on
Hi all,
in todays hangout Alex asked whether kwin binary is going to be renamed to
kwin5 to make it possible to co-install plasma 1 and plasma 2.
My opinion of that is, that we don't need to have things co-installable. After
all kde-workspace doesn't provide libraries where it is useful to have
