All KConfig files inherit kdeglobals keys by default, good or bad?

Aurélien Gâteau agateau at kde.org
Tue Jul 9 09:42:44 BST 2013


On Thursday 04 July 2013 01:28:16 Aaron J. Seigo wrote:
> On Tuesday, June 25, 2013 10:10:03 Aurélien Gâteau wrote:
> > > Why would the code be specific to kiosk? - You asked for an example, not
> > > justification.
> > 
> > I asked for an example, you provided one about kiosk, I answer how your
> > kiosk example is actually painful.
> 
> As someone who has done deployments spanning 100s of systems at a blow, this
> feature is absolutely critical. Please don't kill one of our enterprise
> features.

Did this as well. Unexpected inheritance was a pain.
> 
> Moreover, it is not magic behaviour. It is DEFINED behaviour. It is magic
> only if you are oblivious to it, which can explain any number of features
> in our API. Icon theme inheritance? Magic!
> 
> If you can describe an alternative mechanism to transparently provide global
> settings to applications, let me know.

What we are leaning to is to just make the inheritence parameter mandatory, so 
that developers can make an informed decision.

Aurélien




More information about the kde-core-devel mailing list