Running a Gentoo up-to-date installation. When I attempt to install KDE 3.4
using Konstruct, it bombs out here:

checking for sgmltools... no
checking for fig2dev... no
checking dependency style of ... none
configure: error: conditional "HAVE_XV" was never defined.
Usually this means the macro was only invoked conditionally.
make[2]: *** [configure-work/xine-lib-1.0/configure] Error 1
make[2]: Leaving directory `/home/ralvy/konstruct/libs/xine-lib'
make[1]: *** [dep-../../libs/xine-lib] Error 2
make[1]: Leaving directory `/home/ralvy/konstruct/kde/kdemultimedia'
make: *** [dep-../../kde/kdemultimedia] Error 2

I have xine-libs installed on my system. Not sure what else is need to make
this go away.

Ralph Alvy <ralvy@warpmail.net> wrote:

> Running a Gentoo up-to-date installation. When I attempt to install KDE 3.4
> using Konstruct

Why? KDE 3.4 is available as part of the testing tree via Portage. It
seems to work for most people who've tried it from what I've heard.

--
Andy.

Andy Fraser wrote:

> Ralph Alvy <ralvy@warpmail.net> wrote:
>
>> Running a Gentoo up-to-date installation. When I attempt to install KDE
>> 3.4 using Konstruct
>
> Why? KDE 3.4 is available as part of the testing tree via Portage. It
> seems to work for most people who've tried it from what I've heard.
>
Well, I'm insecure about going out of the stable tree, and, quite frankly,
am not all that sure how I do with just KDE 3.4, leaving the rest of my
system alone. I've been reading posts here and there, after doing a Google
search on upgrading to KDE 3.4. Based on what one person said, I need to
create a file called /etc/portage/package.unmask, and place the following
in it:

kde-base/kde-meta
kde-base/kdeaccessibility-meta
kde-base/kdeaddons-meta
kde-base/kdeadmin-meta
kde-base/kdebase-meta
kde-base/kdeedu-meta
kde-base/kdegames-meta
etc.

But based on what someone else said, instead I would
create /etc/portage/package.keywords and then place this in it:

sys-libs/db ~x86
dev-libs/boost ~x86
kde-base/arts ~x86
kde-base/kdebase-pam ~x86 ...

Ralph Alvy wrote:
> Andy Fraser wrote:
>
>
>>Ralph Alvy <ralvy@warpmail.net> wrote:
>>
>>
>>>Running a Gentoo up-to-date installation. When I attempt to install KDE
>>>3.4 using Konstruct
>>
>>Why? KDE 3.4 is available as part of the testing tree via Portage. It
>>seems to work for most people who've tried it from what I've heard.
>>
>
> Well, I'm insecure about going out of the stable tree, and, quite frankly,
> am not all that sure how I do with just KDE 3.4, leaving the rest of my
> system alone.
>
> But based on what someone else said, instead I would
> create /etc/portage/package.keywords and then place this in it:
>
> sys-libs/db ~x86
> dev-libs/boost ~x86
> kde-base/arts ~x86
> kde-base/kdebase-pam ~x86 ...
>
>
I did put the following in my package.keywords
kde-base/arts ~x86
kde-base/kdebase ~x86
kde-base/kdegraphics ~x86
kde-base/kdeaccessibility ~x86
kde-base/kdewebdev ~x86
kde-base/kdeadmin ~x86
kde-base/kdeartwork ~x86
kde-base/kdeutils ~x86
kde-base/kdepim ~x86
kde-base/kdemultimedia ~x86
kde-base/kdeaddons ~x86
kde-base/kdetoys ~x86
kde-base/kdenetwork ~x86
kde-base/kdeedu ~x86
kde-base/kdegames ~x86
kde-base/kdebase-pam ~x86
kde-base/kdelibs ~x86
sys-libs/db ~x86
dev-libs/boost ~x86
kde-base/kde ~x86

Emergeing KDE 3.4 went fine and as always with the KDE installations, each
minor version gets it's own directory, /usr/kde/3.3 /usr/kde/3.4 ...
Which makes you can have two different versions installed, which you can't
with the bloated Gnome2.

As long as you don't unemerge your earlier KDE install (3.3 I guess), you will
still get notifications about updates to the stabel version too.


//Aho

J.O. Aho wrote:

> Ralph Alvy wrote:
>> Andy Fraser wrote:
>>
>>
>>>Ralph Alvy <ralvy@warpmail.net> wrote:
>>>
>>>
>>>>Running a Gentoo up-to-date installation. When I attempt to install KDE
>>>>3.4 using Konstruct
>>>
>>>Why? KDE 3.4 is available as part of the testing tree via Portage. It
>>>seems to work for most people who've tried it from what I've heard.
>>>
>>
>> Well, I'm insecure about going out of the stable tree, and, quite
>> frankly, am not all that sure how I do with just KDE 3.4, leaving the
>> rest of my system alone.
> >
>> But based on what someone else said, instead I would
>> create /etc/portage/package.keywords and then place this in it:
>>
>> sys-libs/db ~x86
>> dev-libs/boost ~x86
>> kde-base/arts ~x86
>> kde-base/kdebase-pam ~x86 ...
>>
>>
> I did put the following in my package.keywords
> kde-base/arts ~x86
> kde-base/kdebase ~x86
> kde-base/kdegraphics ~x86
> kde-base/kdeaccessibility ~x86
> kde-base/kdewebdev ~x86
> kde-base/kdeadmin ~x86
> kde-base/kdeartwork ~x86
> kde-base/kdeutils ~x86
> kde-base/kdepim ~x86
> kde-base/kdemultimedia ~x86
> kde-base/kdeaddons ~x86
> kde-base/kdetoys ~x86
> kde-base/kdenetwork ~x86
> kde-base/kdeedu ~x86
> kde-base/kdegames ~x86
> kde-base/kdebase-pam ~x86
> kde-base/kdelibs ~x86
> sys-libs/db ~x86
> dev-libs/boost ~x86
> kde-base/kde ~x86
>
> Emergeing KDE 3.4 went fine and as always with the KDE installations, each
> minor version gets it's own directory, /usr/kde/3.3 /usr/kde/3.4 ...
> Which makes you can have two different versions installed, which you can't
> with the bloated Gnome2.
>
> As long as you don't unemerge your earlier KDE install (3.3 I guess), you
> will still get notifications about updates to the stabel version too.
>
>
> //Aho
So I don't need to mess with /etc/portage/package.unmask?

Ralph Alvy wrote:

> So I don't need to mess with /etc/portage/package.unmask?

No, it's not needed since 3.4_rc1.


//Aho