Hi tpowa,
Since you are the resident KDE guy, I was curious as to how you're going to handle kde4 when it releases this month. Most sources say that we should consider this more of a developer release, and stability and polish can be expected only from KDE 4.1. So, a couple of questions:
1. Will you get the KDE packages earlier than the actual release date, as you always seem to do? 2. Do you plan on moving these packages to extra or testing...or maybe even unstable?? 3. What naming scheme will you use? Will KDE4 packages become 'kdelibs' 'kdebase' and so on, or will kde3 packages retain that nomenclature for a while? (looking at how qt4=>qt in testing, I presume kde4=>kdelibs/kdebase). This means kde3 packages have to be rebuilt with the new naming scheme kdebase3, and of course all dependent packages with it.
I just thought I'll get the ball rolling on the inevitable confusion to follow :)
Thanks, Varun
On Tuesday 08 January 2008 20:24:01 Varun Acharya wrote:
Hi tpowa,
Since you are the resident KDE guy, I was curious as to how you're going to handle kde4 when it releases this month. Most sources say that we should consider this more of a developer release, and stability and polish can be expected only from KDE 4.1. So, a couple of questions:
- Will you get the KDE packages earlier than the actual release date, as
you always seem to do? 2. Do you plan on moving these packages to extra or testing...or maybe even unstable?? 3. What naming scheme will you use? Will KDE4 packages become 'kdelibs' 'kdebase' and so on, or will kde3 packages retain that nomenclature for a while? (looking at how qt4=>qt in testing, I presume kde4=>kdelibs/kdebase). This means kde3 packages have to be rebuilt with the new naming scheme kdebase3, and of course all dependent packages with it.
I just thought I'll get the ball rolling on the inevitable confusion to follow :)
Thanks, Varun
Hi here the current state from my point of view: kde4 4.0 series is pure crap for end users. The real replacement status will hopefully come with 4.1 series. I will not ship kde4 for extra until it's a full replacement for 3.x series.
The names should stay and a kde3/kde4 parallell mess is not worth at the moment.
I have a full build environment here and probably i'll place it somewhere that others can use it too. (an other repository or unstable, but with no kdelibs4 or kdebase4 name scheme!) But it's far away from 3.x feature richness nor usability. Monthly or every 2 months a svn snapshot of the trunk(4.1 development) would make much more fun than the crippled 4.0 series.
greetings from kde4 kmail :) tpowa
Tuesday 08 January 2008, Varun Acharya wrote: | I just thought I'll get the ball rolling on the inevitable | confusion to follow :)
kde4 depends on qt4 and this is waiting for pacman 3.1
the only place it can go now is testing.
after we process our stack, i would suggest to put it in unstable with kde*4 naming... and once it gets mature enough, we can switch the names.
- D
On Tuesday 08 January 2008 21:30:17 Damir Perisa wrote:
Tuesday 08 January 2008, Varun Acharya wrote: | I just thought I'll get the ball rolling on the inevitable | confusion to follow :)
kde4 depends on qt4 and this is waiting for pacman 3.1
the only place it can go now is testing.
after we process our stack, i would suggest to put it in unstable with kde*4 naming... and once it gets mature enough, we can switch the names.
- D
hi
First it needs a usable state and this is not the fact right now. and kde 4.0 series will never get a usable state it's frozen and will not get new features anytime, 4.1 is scheduled in half a year or 9 months then it's worth to think about a road to go with conflicts and such things not before that.
greetings tpowa
Tuesday 08 January 2008, Tobias Powalowski wrote: | On Tuesday 08 January 2008 21:30:17 Damir Perisa wrote: | > Tuesday 08 January 2008, Varun Acharya wrote: | > | I just thought I'll get the ball rolling on the inevitable | > | confusion to follow :) | > | > kde4 depends on qt4 and this is waiting for pacman 3.1 | > | > the only place it can go now is testing. | > | > after we process our stack, i would suggest to put it in | > unstable with kde*4 naming... and once it gets mature enough, we | > can switch the names. | > | > - D | | hi
hi :)
| First it needs a usable state and this is not the fact right now. | and kde 4.0 series will never get a usable state it's frozen and | will not get new features anytime, 4.1 is scheduled in half a year | or 9 months then it's worth to think about a road to go with | conflicts and such things not before that.
i agree. i'm only suggesting that this kde4-devel (svn snaps) pkgs can be put in unstable, as a place to put -devel things that someone wants to try. this way we do not need an extra repo for them. (the whole thing is reallly only a detail)
- D
arch-dev-public@lists.archlinux.org