Making Purpose part of KF5

Aleix Pol aleixpol at kde.org
Fri Nov 10 15:32:23 UTC 2017


On Fri, Nov 10, 2017 at 1:20 PM, Hartmut Goebel
<h.goebel at crazy-compilers.com> wrote:
> Am 10.11.2017 um 12:50 schrieb Aleix Pol:
>> I share the concern in fact, part of the reason why I didn't push it
>> earlier was to be able to have it proper tier2. My reasoning for
>> leaving it as this is that it just adds an extra step users will have
>> to take to install the plugins and it's not a very useful one (to pull
>> the plugins). Without plugins, purpose is useless.
>
> This means: purpose is the framework and ought to be in"frameworks".
> Maybe it should be called "purpose-framework" to emphasis this.
>
> The plugins have more dependencies and should not go into the framework,
> though.
>
> If purpose would introduce higher level dependencies, how should this be
> build then? You'll end up with cyclic dependencies, which are a horror
> to build.
>
> Please move the plugins into a separate repository or at least make them
> to be build *completely* separate (like a subproject.)

The fact that there's plugins in the repository now doesn't mean by
far that there can't be plugins inside.

For example note that kio has some ioslaves in src/ioslaves and I'd
say that's perfectly fine.

Aleix


More information about the Kde-frameworks-devel mailing list