<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">Le 13 mai 2017 14:18, "David Faure" <<a href="mailto:faure@kde.org">faure@kde.org</a>> a écrit :<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="elided-text">On lundi 8 mai 2017 13:09:03 CEST Luigi Toscano wrote:<br>
> Matthieu Gallien ha scritto:<br>
> > Hello,<br>
> ><br>
> > Currently KFileMetaData is a tier 2 framework even when you remove all<br>
> > optional dependencies on other frameworks due to a dependency on ki18n.<br>
> ><br>
> > I would like to know if people think it would be possible to transition it<br>
> > to depend on Qt for i18n so as to lower its tier ?<br>
> ><br>
> > Currently, ki18n is used to provide localized name for properties on file.<br>
> ><br>
> > I would like to get more people to use it outside core KDE software. For<br>
> > example, people could use it for music players built on top of Qt. I<br>
> > believe lowering the tier can help this.<br>
> ><br>
> > What do you think ?<br>
><br>
> Even if the usage of KI18n is limited and it could be replaced with the Qt<br>
> native system (basic strings, no arguments), I'm not sure that you can<br>
> officially lower the tier with optional dependencies. Others may remember<br>
> better of course.<br>
<br>
</div>Let's not debate semantics of tiers. What really matters is that if<br>
KFileMetaData has optional dependencies on other frameworks, then chances are<br>
quite high that Linux (and other) distributions will provide binary packages<br>
of KFileMetaData *with* these dependencies compiled in. So in practice your<br>
music player will depend on these optional dependencies anyhow, so "tier2" is<br>
more correct than "tier1".<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">My music player is using ki18n and I am happy with it. I am still hoping KFileMetaData could be useful by itself not necessarily linked to other frameworks. Improving the documentation would be the next task to do.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
It only makes a difference for people who compile from sources, they can<br>
choose to skip the optional deps and therefore have less things to compile.<br>
This is very valuable of course, and I'm all for it (it lowers the bar for<br>
contributions).<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">This is my main motivation.</div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<font color="#888888"><br>
--<br>
David Faure, <a href="mailto:faure@kde.org">faure@kde.org</a>, <a href="http://www.davidfaure.fr" rel="noreferrer" target="_blank">http://www.davidfaure.fr</a><br>
Working on KDE Frameworks 5<br></font></blockquote></div></div></div></div>