KDE 4 in gentoo portage?

Message

xiando · Post by **xiando** » Sat Apr 26, 2008 5:44 pm

ufoman wrote:I confirm the SSL issue. I even filed a bug to KDE bugzilla about my experiences https://bugs.kde.org/show_bug.cgi?id=160394, but I did not get any response yet.

Install qca-ossl. This is a Gentoo bug, not a KDE bug, the builds do not have qca-ossl as dep.

Lori · Post by **Lori** » Sun Apr 27, 2008 1:53 am

xiando wrote:
ufoman wrote:I confirm the SSL issue. I even filed a bug to KDE bugzilla about my experiences https://bugs.kde.org/show_bug.cgi?id=160394, but I did not get any response yet.
Install qca-ossl. This is a Gentoo bug, not a KDE bug, the builds do not have qca-ossl as dep.

I do have qca-ossl-2.0.0_beta3 installed and it doesn't solve the issue. Comment #3 in the above mentioned bug report also says that qca-ossl is unrelated. Someone on this thread mentioned that it's a Qt-4.3 bug, solved in Qt-4.4.

Hum · Post by **Hum** » Tue Apr 29, 2008 2:56 am

El_Presidente_Pufferfish wrote:
jurrie wrote:- I get "Protocol not supported" messages when entering an uri without http:// (edit: fixed after installing kde-meta)
You wouldn't happen to be able to narrow that down, would you?

I have the same protocol not supported message too. I think it might be a useflag i'm missing but I really don't know since it never really bothered me since i use firefox.

rek2 · Post by **rek2** » Wed Apr 30, 2008 4:40 pm

http://www.kde.org/announcements/announ ... alpha1.php

Lori · Post by **Lori** » Wed Apr 30, 2008 5:20 pm

Are there going to be ebuilds for this early release, or people who want to get a sneak peek into 4.1 will still have to use the KDE overlay? But since the overlay now needs Paludis, I highly doubt there will be ebuilds, especially not before Portage will support the features they use for the overlay ebuilds. This of course is pure speculation

Tolstoi · Post by **Tolstoi** » Thu May 01, 2008 7:37 am

Is it worth testing meanwhile? I tried out 4.0.0 or something like that and went back to 3.5.

ArneBab · Post by **ArneBab** » Thu May 01, 2008 12:58 pm

Lori wrote:Are there going to be ebuilds for this early release, or people who want to get a sneak peek into 4.1 will still have to use the KDE overlay? But since the overlay now needs Paludis, I highly doubt there will be ebuilds, especially not before Portage will support the features they use for the overlay ebuilds. This of course is pure speculation

Why does the overlay need paludis?

beso_1717 · Post by **beso_1717** » Thu May 01, 2008 3:45 pm

ArneBab wrote:
Lori wrote:Are there going to be ebuilds for this early release, or people who want to get a sneak peek into 4.1 will still have to use the KDE overlay? But since the overlay now needs Paludis, I highly doubt there will be ebuilds, especially not before Portage will support the features they use for the overlay ebuilds. This of course is pure speculation
Why does the overlay need paludis?

cause portage doesn't support the new build system, and it won't for quite a time. but if you're not a real experimentator then i'd suggest you to stay away from the overlay.

ArneBab · Post by **ArneBab** » Fri May 02, 2008 10:16 pm

I just read up about paludis (again), and I don't really like the attitude I read on the website that much - "learn to use nice" as one example... but I'll stop it here (no need to fire up a flamewar or such - some people like it, some don't, and I like a python based distro, some do so, others don't... as long as I don't help out in programming, I think I should keep out a bit).

So I hope that portage will support the new build system as soon as KDE 4.1 is stable enough to test (where can I find information on the build system?).

beso_1717 · Post by **beso_1717** » Fri May 02, 2008 11:37 pm

ArneBab wrote:I just read up about paludis (again), and I don't really like the attitude I read on the website that much - "learn to use nice" as one example... but I'll stop it here (no need to fire up a flamewar or such - some people like it, some don't, and I like a python based distro, some do so, others don't... as long as I don't help out in programming, I think I should keep out a bit).

So I hope that portage will support the new build system as soon as KDE 4.1 is stable enough to test (where can I find information on the build system?).

i've been using portage and paludis for some time and both have flaws and good points.
paludis is fast at getting the world for update at the first update after the pc has been startup and has a very good overlay management together with a lot of config split options (you could split your conf files one per package if you need) and has a very good share of hooks that make its behaviour better.
portage has the buildpkg option that paludis doesn't and doesn't need external hooks when building some core packages (like baselayout) while paludis does or you risk some pain in fixing stuff up.
paludis instead is very slow to build (it builds a lot of clients like the reconcilio the broken linkage rebuilder) and takes quite some time to do so: it builds only with -j1 since it has problems otherwise, taking about 2 hours when compiling totally in ram and with test disabled (the paludis test phase takes about 2-3 hours to complete and it makes me mad), while portage installs in less than 1 minute.
anyway, as a personal experience you just add the nice option (the paludis wrapper hook does this for you) and then the usual paludis options that you always want in the user .bashrc (like --dl-reinstall if-use-changed) and whenever you run paludis world -ip you'll also trigger the reinstall if use changed.
to me paludis is good and fast and you could also make per package cflags, ldflags and so on configuration (that i don't know if it's possible with portage), you can disable sandbox per package and not always as with portage and it's a little more configurable than portage.
again, if it's the first time you'lll use it try not to start with kde4-overlay but with some package that you used to build with portage first to see how it works and how you can configure paludis. after that you could try out something that continues to work some days and break after that (the kde4 trunk overlay).

Maliwik · Post by **Maliwik** » Sat May 03, 2008 2:46 am

I typed emerge -avD kde-base/kde-meta:kde-4 and it gets to esound and fails after trying to run aclocal. I've searched for this problem all over the forums and bugzilla and all the solutions that other people have come across do not work for me. Is there any way to skip esound in this or would there perhaps be another aclocal problem later on?

--Mike

beso_1717 · Post by **beso_1717** » Sat May 03, 2008 9:38 am

Maliwik wrote:I typed emerge -avD kde-base/kde-meta:kde-4 and it gets to esound and fails after trying to run aclocal. I've searched for this problem all over the forums and bugzilla and all the solutions that other people have come across do not work for me. Is there any way to skip esound in this or would there perhaps be another aclocal problem later on?

--Mike

why do you use gnome sound server with kde?! is there any reason for that?! kde has arts or you could build everything on pulseaudio or jack, that are independent from the display manager and are supported by all apps.

Maliwik · Post by **Maliwik** » Sat May 03, 2008 2:52 pm

Actually, I thought I might have had the gnome USE flags set in make.conf but I don't.

The esound package automatically tries to emerge whenever I try to emerge kde4.0 so I'm not sure what's wrong with it. I think there was a total of 447 packages that tried to emerge when I typed that and esound was around the 160th package or so. I can't get passed esound though because of an aclocal error.

beso_1717 · Post by **beso_1717** » Sat May 03, 2008 5:04 pm

Maliwik wrote:Actually, I thought I might have had the gnome USE flags set in make.conf but I don't.

The esound package automatically tries to emerge whenever I try to emerge kde4.0 so I'm not sure what's wrong with it. I think there was a total of 447 packages that tried to emerge when I typed that and esound was around the 160th package or so. I can't get passed esound though because of an aclocal error.

put

Code: Select all

-gtk -esd -gnome

flags in make.conf. there is surely there some bad package that has esound enabled by default and that one is pushing a looooot of unneeded packages: 400+ packages are surely wrong for a kde4 installation; i've got about 120 packages including the world updates. i barely have 400 packages in world so there's surely an use flag issue somewhere.

Maliwik · Post by **Maliwik** » Sat May 03, 2008 6:30 pm

Thank you for the reply,

That got me further, but now I get an autoconf error with fontconfig-2.5.0-r1.
Here's my make.conf (it's probably completely wrong, but I followed the instructions in the gentoo handbook and the kde4.0 instructions)

Code: Select all

CFLAGS="-02 -pipe"
CXXFLAGS="-02 -pipe"

CHOST="x86_64-pc-linux-gnu"

USE="-gtk -esd -gnome mmx sse sse2 qt3 qt4 kde dvd alsa cdr"
MAKEOPTS="-j3"
ACCEPT_KEYWORDS="~amd64"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="nvidia"

Is there something wrong with my make.conf or is my Portage install completely borked?

--Mike

beso_1717 · Post by **beso_1717** » Sat May 03, 2008 7:00 pm

Maliwik wrote:Thank you for the reply,

That got me further, but now I get an autoconf error with fontconfig-2.5.0-r1.
Here's my make.conf (it's probably completely wrong, but I followed the instructions in the gentoo handbook and the kde4.0 instructions)

i've had some autoconf errors on various packages like samba, libgdiplus and there wasn't anything wrong. after one or two days everything went ok. for the moment just hard mask the package that fails (fontconfig-2.5.0-r1 in your /etc/portage/package.mask and that should have it work if some specific package wouldn't be dependent of that specific version that you've masked).

Maliwik wrote:
Code: Select all
CFLAGS="-02 -pipe"
CXXFLAGS="-02 -pipe"

CHOST="x86_64-pc-linux-gnu"

USE="-gtk -esd -gnome mmx sse sse2 qt3 qt4 kde dvd alsa cdr"
MAKEOPTS="-j3"
ACCEPT_KEYWORDS="~amd64"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="nvidia"
Is there something wrong with my make.conf or is my Portage install completely borked?

--Mike

i think that your autconf problem might be related to the amd64 unstable branch, but as i've said, for the moment just hard mask the packages that fail to auconf and try them after a reboot or after some days usually they build fine (don't ask me why this happens). as for the use flags, i'll add qt3support and qt also. also the following packages really need gtk enabled flag enabled so you should enable it in /etc/portage/package.use:

Code: Select all

app-text/poppler-bindings qt3 gtk
media-video/mplayer 3dnow 3dnowext mmxext xvmc v4l2 rtc -real rar lzo live enca cpudetection amr gtk dvdnav mp3 mp2 sdl svga win32codecs srt
net-im/pidgin networkmanager gtk
net-www/mplayerplug-in divx gmedia gtk quicktime realmedia wmp mplayer-bin

the other flags are the flags i use for these packages but are not at all manadatory.

Maliwik · Post by **Maliwik** » Sat May 03, 2008 8:26 pm

How do you hardmask packages?

(Sorry for my complete lack of understanding of Portage)

Will this let me install kde4 if I don't have the package emerged? I put media-libs/fontconfig in package.mask and when I ran emerge -avD kde-base/kde-meta:kde-4 it said "All ebuilds that could satisfy "media-libs/fontconfig" have been masked." Then it says towards the bottom "(dependency required by "x11-libs/qt-gui-4.4.0_rc1" [ebuild]).

I'm clueless =(

beso_1717 · Post by **beso_1717** » Sat May 03, 2008 9:30 pm

Maliwik wrote:How do you hardmask packages?

(Sorry for my complete lack of understanding of Portage)

Will this let me install kde4 if I don't have the package emerged? I put media-libs/fontconfig in package.mask and when I ran emerge -avD kde-base/kde-meta:kde-4 it said "All ebuilds that could satisfy "media-libs/fontconfig" have been masked." Then it says towards the bottom "(dependency required by "x11-libs/qt-gui-4.4.0_rc1" [ebuild]).

I'm clueless =(

well, kde-4.0.x won't build on qt-4.4.x or on qt-splits or will build and not work. so for qt and kde-4.0.x from portage you'll need qt-4.3. for the fresh trunk kde4 version you'll need to go with paludis since there's a new build system and qith qt-4.4, but for 4.0.x you just downgrade to 4.3 and remove the qt name from package.unmask (qt-4.4 is repository masked for what i know).
for the fontconfig issue you just need to mask the single version that failed like this:

Code: Select all

=media-libs/fontconfig-2.5.0-r1

you'r media-libs/fontconfig would mask every version of fontconfig, and not just the one you wanted to mask.
there are also other options:
if you want to mask packages that would come out from a new version, let's say for example qt major than 4.3.4 you could do the following:

Code: Select all

>x11-libs/qt-4.3.4

this code would manually mask all qt versions that are named 4.3.5, or 4.4.x etc. you could also do something like this:

Code: Select all

>=x11-libs/qt-4.4_rc1

which means all qt versions major or equal than 4.4_rc1. just be sure to put a version (full version) when using "= > <".

Maliwik · Post by **Maliwik** » Sat May 03, 2008 9:41 pm

Cool, thank you much on that. That clears a lot up.

I've decided to do a fresh install of Gentoo because I have a feeling I've messed something up somewhere along my emerging-spree and I'm not entirely sure how to go about fixing it all. Now that I know how to work Portage (somewhat) more than I used to, I should be able to run things smoother on this install (hopefully) =P

Thanks for your help beso_1717 =)

--Mike

Maliwik · Post by **Maliwik** » Mon May 05, 2008 2:35 pm

Maybe I'm just a total noob at this, but what do I do once I emerge all of KDE4? I read the install guide and it doesn't go about explaining how to set it up. I put startkde in .xinitrc (which is how I did it on other distros) and it said "startkde: command not found".

--Mike

beso_1717 · Post by **beso_1717** » Mon May 05, 2008 3:32 pm

Maliwik wrote:Maybe I'm just a total noob at this, but what do I do once I emerge all of KDE4? I read the install guide and it doesn't go about explaining how to set it up. I put startkde in .xinitrc (which is how I did it on other distros) and it said "startkde: command not found".

--Mike

i've never did something like that. you'll just need to have

Code: Select all

DISPLAYMANAGER="kdm"

in /etc/conf.d/xdm.

if you're on unstable amd64 then you'll use openrc 2.3.0 and should just add xdm at default with rc-update add xdm default.

this would start xdm once it is possible and will have you do the login via kdm. if something doesn't work then reemerge kdebase-startkade package (it's a meta one) and kdebase-meta (or kdebase) and that should put everything needed to have your kde environment up and working.
[/code]

Maliwik · Post by **Maliwik** » Mon May 05, 2008 3:52 pm

emerge starkde?

The way I did it was just emerge the x11-xorg package and then the kde4 package.

Was I supposed to emerge startkde before I emerged kde4?

EDIT: And I put the display manager line in the xdm file but I'm still not certain as how to start up kde4. Whenever I type startx it still boots into twm.

EDIT2: Well, I typed startx and booted into twm and then tried typing startkde in one of the terminals in twm. Low and behold, it booted into KDE! Now I just need to figure out how to get the menu bar showing and all the other stuff (which I'll scour around for =P)

--Mike

ArneBab · Post by **ArneBab** » Mon May 05, 2008 5:57 pm

If you already used KDE 3 before KDE 4, you should simply be able to switch in KDM.

As first start, please look at

/etc/conf.d/xdm

And check if you have a line saying

DISPLAYMANAGER="kdm-4.0"

After that try

/etc/init.d/xdm start

--- oh well ... too slow

---

Maliwik · Post by **Maliwik** » Mon May 05, 2008 7:08 pm

Thanks for the tip.

I found out my problem. I was typing startkde from an xterm in twm and that's why the panel wouldn't load. I decided to put "startkde" in my .xinitrc file and then typed startx and everything loaded up perfectly. =)

--Mike

Ivanich_ · Post by **Ivanich_** » Wed May 07, 2008 9:34 am

KDE 4.0.4 released

KDE 4 in gentoo portage?

qca-ossl

Re: qca-ossl

kde ship 4.1-alpha1