El Dilluns, 8 de juliol de 2013, a les 15:10:06, =C0lex Fiestas va escr=
iure:
> On Thursday 04 July 2013 21:39:03 Albert Astals Cid wrote:
> > I agree we are too late.
> >=20
> > If KScreen is so much better, i'd make sure packagers know about it=
 and
> > they can install KScreen and not KRandR if they want, even provide
> > replaces/conflicts rules.
> >=20
> > But since we are 5 days away from "Release Candidate" day, don't th=
ink
> > removing (or disabling) something from kde-workspace is a good idea=
.
> >=20
> > Cheers,
> >=20
> >   Albert
> >  =20
> > > Cheers !
>=20
> Have you taken into account that kde-workspace will be frozen startin=
g in
> 4.11 so this is our only chance of removing deprecated/not supported/=
not
> working well software?

I have, I've also taken into account that if you remove it we will be s=
hipping=20
a workspace with no software at all to configure your screens for a lon=
g time.=20

Ok, there's a different software that works better, but this one seems =
to work=20
for some people (or at least won't kill their puppies) and the other on=
e is=20
distributed in an "extra" tarball.

> If you have, and you still haven't changed your mind, I will do the
> following if everybody is ok with it:
>=20
> -Add a README in KRandR folder warning that the software is known to =
be not
> working well, and that they should use kscreen

"known for not working well" seems like a bit of FUD, if there's known =
errata,=20
we should explain the cases in which it doesn't work. Because I'm using=
 it and=20
works for my use case so "known for not working well" is too broad and =
fear-
creating.

> -Add a warning in the release notes, somewhere.
> -Send an email to kde-packagers
> -Anything more?

That works for me

Cheers,
  Albert

>=20
> Cheers and thanks for the feedback !