Message: previous - next
Month: April 2012

Re: Re: [trinity-devel] Re: Resolving the TWin/KWin Fork Issue

From: Martin Gräßlin <mgraesslin@...>
Date: Sat, 28 Apr 2012 11:29:44 +0200
On Friday 27 April 2012 11:05:12 Darrell Anderson wrote:
> > I mean if we started using kwin, we would definitely have
> > influence upon it because we would be the users. Reporting
> > bugs requesting features. I am not sure what else you mean
> > by "influence". KWin4 does everything TWin does.
> One of the points of contention with this and other related topics is how
> much influence do KDE4 users have? Please notice I did not write users have
> no influence. Nor did I write developers don't listen or respond to users.
> I only asked rhetorically how much influence.
> Consider that nepomuk/akonadi/strigi remain non negotiables, despite users
> requesting this from Day One. The argument that these services can be
> disabled is not the same as not installing them in the first place. When
> other apps depend upon the libraries of those three packages then disabling
> the services accomplishes little. The overhead remains. The dependencies
> remain.
> Many non enterprise users have no need or interest in social networking,
> regardless of the potential merits. The entire nepomuk/akonadi/strigi
> philosophy never has been optional within KDE4. Few people have argued that
> those features be ripped from KDE4. They argued that they should be
> optional. Truly optional. People who run a half dozen KAlarm events and
> check email twice a day don't need or want a caching engine running in the
> background. They don't care about sharing desktops or activities with other
> people. They don't care or need massive meta data indexing.
> Yet building KDE4 without those three modules is not possible.
Please, please do your homework before doing such statements:
* akonadi *not* a mandatory build dependency
* strigi *not* a mandatory build dependency
* nepomuk *not* a mandatory build dependency

I have pointed out this point several times on this mailing list. And still 
this wrong statement is done.

Akonadi is only a build dependency for Kontact and Akonadi has been developed 
for it. But it's not a requirement to use Kontact at all. It's an advanced 
application not targeting the "average" users (those who do complain btw).

Please also note that KDE only provides sources. It's the distribution's task 
to compile the software, so any request to have *packages* without 
Nepomuk/Akonadi/Strigi has to go to the distributions and *not* to the KDE 

Thanks for no longer spread misinformation about KDE.

Martin Gr��lin