Muon and kde-gtk-config moved to kde/workspace - was - Re: Moving repositories in the module structure
luigi.toscano at tiscali.it
Wed Oct 8 21:39:51 BST 2014
Aleix Pol ha scritto:
> On Wed, Oct 8, 2014 at 9:59 PM, Albert Astals Cid <aacid at kde.org
> <mailto:aacid at kde.org>> wrote:
> El Dimecres, 8 d'octubre de 2014, a les 21:02:32, Aleix Pol va escriure:
> > On Tue, Oct 7, 2014 at 3:13 PM, Thomas Pfeiffer <thomas.pfeiffer at kde.org <mailto:thomas.pfeiffer at kde.org>>
> > wrote:
> > > On Sunday 05 October 2014 20:30:33 Albert Astals Cid wrote:
> > > > > The reasoning is that this way they will be released together with
> > >
> > > Plasma
> > >
> > > > > Workspace.
> > > >
> > > > I don't see that anyone can have a problem with kde-gtk-config.
> > >
> > > Risking that someone might kill me for saying this:
> > > Given that this configures how GTK applications work inside Plasma and not
> > > inside the KDE community, shouldn't it be renamed to plasma-gtk-config so
> > > we
> > > don't add to the branding confusion with our own package names?
> kde-gtk-config does not configure how GTK applications work inside of
> Plasma, is
> the Gtk theme Configurator made by KDE.
> I'm almost sure that if you use kde-gtk-config in non plasma it will still
> change how gtk apps look line.
> > To be honest, I don't care. In fact it used to be called Chakra GTK Config.
> > It will need somebody to do the change (I can do it, at least on the kde
> > side) and it will require distros to adopt the new name, but if it is going
> > to make someone's life easier I'm all for it.
> > Aleix
> Well, on the other hand it's thought to be used from the systemsettings. A 3rd
> party project would have to trigger the kcmshell5 or create a separate kcm
> integration system.
Isn't it the same path that 3rd party projects need to do to use/let use
configure stuff like proxy, web shortcuts, etc...? Amarok could run the Phonon
KCM for a while.
More information about the kde-core-devel