You are not logged in.
Hello guys,
Some one have time to compile this package and add it to testing?
And please, if you will compile it, compile with flag full-debug. It'll be more flexible, and helpfull with reporting a bug for kde developers.
http://kde.org/announcements/announce-4.3-rc1.php
Best regards.
Last edited by cojack (2009-07-05 06:18:41)
Offline
There is the kde-unstable repo. I guess it will be updated to rc1 soon (if not already?)
Offline
Can you give me the link? There is any how to install it?
Offline
Offline
Can you give me the link? There is any how to install it?
from newsletter:
[kde-unstable]
Include = /etc/pacman.d/mirrorlist
how to install: http://wiki.archlinux.org/index.php/KDE_Packages
Give what you have. To someone, it may be better than you dare to think.
Offline
Please note that you'll need testing repo and you should know how to use it.
Offline
I has spend all my yesterday to install this repo, and resolving many problems... And newer again install anything out of core, extra, community...
Offline
I has spend all my yesterday to install this repo, and resolving many problems... And newer again install anything out of core, extra, community...
Lesson learned
But its a good feeling when its running
Offline
OK, try kdemod-testing, is much better...
I do not speak English, but I understand...
Offline
http://kde.org/announcements/announce-4.3-rc3.php
4.3 RC3 released today.
Excuse my poor English.
Offline
It has been asked many times, but I have never seen an answer from the developers: why are the KDE packages in [kde-unstable] not built with debug information? Creating our own PKGBUILDs and recompiling them seems like an unnessessary complication for reporting bugs, given that it is a testing repository.
Offline
It has been asked many times, but I have never seen an answer from the developers: why are the KDE packages in [kde-unstable] not built with debug information?
to name a few:
- packages increase dramatically in size
- compilation time increases quite a bit
- backtraces are not that useful as packages linked to in the normal repos don't have debug info
Offline
One of the developers said that the packages began to be very big with debug info.
Nevertheless, it's almost final, the debug info is much useful when we use early pre-alpha,alpha,beta versions (between 4.x.6x and 4.x.8x)
Offline
mutlu_inek wrote:It has been asked many times, but I have never seen an answer from the developers: why are the KDE packages in [kde-unstable] not built with debug information?
to name a few:
- packages increase dramatically in size
- compilation time increases quite a bit
- backtraces are not that useful as packages linked to in the normal repos don't have debug info
Thank you for the response. Given that few people use the testing repos, I think the first two points are not that important, but I might be wrong. The last point is, of course, an issue. I just wish we had separate debug packages in Arch.
Offline
Well, for me the first two points are important, too. The packages are not meant to debug KDE in the first place but testing the new split system, db-scritps etc..
Offline
One day I might implement this bug: http://bugs.archlinux.org/task/10975 . Then we could have separate debug symbol packages.
Offline
I would like a kde-base-meta package which just installs the kde essentials in order to have kdm, kicker, konqueror and dolphin for instance.. just like in gentoo xxD
Offline
I was going to say kde-meta-kdebase, but it does not include kdebase-workspace...
ah well, installing kde-meta-kdebase and kdebase-workspace seems to be enough to get a basic instlall so it's still not very much to type ;-)
Offline
kdebase-workspace is the most minimal workspace you can get. Everything else is optional. And please not the difference between the meta packages and groups: http://wiki.archlinux.org/index.php/KDE_Packages
Offline
kdebase-workspace is the most minimal workspace you can get. Everything else is optional. And please not the difference between the meta packages and groups: http://wiki.archlinux.org/index.php/KDE_Packages
That group thing does not work for me. If I just pacman -S kdeedu, it install stuff from extra. If I do pacman -S kde-unstable/kdeedu, I get this:
warning: provider package was selected (kde-meta-kdeedu provides kdeedu)
Maybe it works when I disable [extra] and then do a pacman -S kdeedu, but this way now it just does not work.
Edit: before someone asks: My repo order in pacman.conf is kde-unstable, testing, core, extra, community.
Last edited by buddabrod (2009-07-24 11:16:00)
Offline
pacman cannot handle this (yet). So you have to wait until KDE 4.3 is in extra.
Offline
One day I might implement this bug: http://bugs.archlinux.org/task/10975 . Then we could have separate debug symbol packages.
You'd be my hero.
Offline
kdebase-workspace is the most minimal workspace you can get. Everything else is optional. And please not the difference between the meta packages and groups: http://wiki.archlinux.org/index.php/KDE_Packages
I know this is in its very early stages, but can anyone tell me approximately how the most minimal kde (kdebase-workspace) would compare to something like xfce? It sounds like with this new ability to start with the minimum and add packages as needed it will be much lighter than before. Just trying to get an idea before I tired it out. Not sure if it would be as quick as something like xfce?
Arch64, AMD64, LXDE
Offline
Pierre wrote:kdebase-workspace is the most minimal workspace you can get. Everything else is optional. And please not the difference between the meta packages and groups: http://wiki.archlinux.org/index.php/KDE_Packages
I know this is in its very early stages, but can anyone tell me approximately how the most minimal kde (kdebase-workspace) would compare to something like xfce? It sounds like with this new ability to start with the minimum and add packages as needed it will be much lighter than before. Just trying to get an idea before I tired it out. Not sure if it would be as quick as something like xfce?
I think you are misunderstanding the thing... You always have a full kde running like always, the only thing that's changed is that you dont need to install the full meta packages at all times. If you want marble for isntance, you just install marble and not the complete kdeedu package.
The running kde is still the same as always. Plasma still consumes the same amount of ram and still needs the same cpu time. The only difference is the lowered disk usage..
So light-weight DE's still have their right to exist
Offline
I think you are misunderstanding the thing... You always have a full kde running like always, the only thing that's changed is that you dont need to install the full meta packages at all times. If you want marble for isntance, you just install marble and not the complete kdeedu package.
The running kde is still the same as always. Plasma still consumes the same amount of ram and still needs the same cpu time. The only difference is the lowered disk usage..
So light-weight DE's still have their right to exist
Ah, I see ...Thanks
Arch64, AMD64, LXDE
Offline