Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-17 Thread Aaron J. Seigo
On Thursday, January 16, 2014 22:24:09 Marco Martin wrote: they are both desiderable, but they seems quite in contrast each other. I'm sure I'm hitting a false dichotomy there, but not seeing a clear solution. does anybody does? there are (at least) two ways to approach the “integrated

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-17 Thread Adriaan de Groot
On Thursday 16 January 2014 22:24:09 Marco Martin wrote: they are both desiderable, but they seems quite in contrast each other. I'm sure I'm hitting a false dichotomy there, but not seeing a clear solution. does anybody does? There shouldn't be a dichotomy. It's a matter of defining and then

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-17 Thread Luigi Toscano
Adriaan de Groot wrote: Note also that we *have* some kinds of metapackages already defined. Thery're on our website, at http://www.kde.org/applications/ . You'll note that the list of applications in graphics doesn't coincide with the repositories, and does include digiKam, because

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-16 Thread Sune Vuorela
On 2014-01-15, Albert Astals Cid aa...@kde.org wrote: tarball? An XML file somewhere? Personally I find distros should be smart enough to decide which apps they want to ship by default and which not. I've actually in my distribution tried to ship stuff, including package selection, quite close

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-16 Thread Adriaan de Groot
On Thursday 16 January 2014 11:56:08 Sebastian Kügler wrote: On Wednesday, January 15, 2014 23:46:29 Adriaan de Groot wrote: On Wednesday 15 January 2014 23:13:11 Albert Astals Cid wrote: Besides how would you define this KDE Essential Applications group? I mean a tarball? An XML file

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-16 Thread Aaron J. Seigo
On Thursday, January 16, 2014 12:15:05 Adriaan de Groot wrote: But I don't think that Scuba-diving C++ programmer is going to be a viable metapackage any time soon. No, but it could be a “Sports and Fitness” metapackage. There are a remarkable number of such apps for Android, for instance.

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-16 Thread Thomas Pfeiffer
On Thursday 16 January 2014 11:56:08 Sebastian Kügler wrote: On Wednesday, January 15, 2014 23:46:29 Adriaan de Groot wrote: On Wednesday 15 January 2014 23:13:11 Albert Astals Cid wrote: Besides how would you define this KDE Essential Applications group? I mean a tarball? An XML file

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-16 Thread Marco Martin
On Thursday 16 January 2014 21:50:47 Thomas Pfeiffer wrote: Is it just me, or does this idea sound like it's going in a similar direction to the Flows Björn and I talked about at Akademy? ;) Tasks/workflows is really what we should be thinking about, because that's the user's perspective,

Re: [kde-community] KDE Essential Applications - was - Re: Applications in KDE Generation 5

2014-01-15 Thread Adriaan de Groot
On Wednesday 15 January 2014 23:13:11 Albert Astals Cid wrote: Besides how would you define this KDE Essential Applications group? I mean a tarball? An XML file somewhere? Personally I find distros should be smart enough to decide which apps they want to ship by default and which not. It's