[gentoo-dev] just a little feedback...

[gentoo-dev] just a little feedback...

[Tibor Rudas]

Hi

Here is the feedback I  promised:

 - thanks for the help with yp/nis but alas it didn't work. the +:::... 
entries did not help but switching from pam_pwdb.so to pam_unix...
did... I guess I'll have to have a closer look at the pam & nis docs...;)

 - lately I am experiencing great difficulties in doing an install from the
1.0_rc5-r4 build iso image...
It worked perfectly well on July 27th where I did the emerge rsync
and the bootstrap. The emerge system followed on July 30th and the
machine is up and running...
During the last week however I tried to install an identical machine
and failed multiple times (and I don't have super bombad racing!).
At first even the new August-based bootsrap file failed because
gettext-0.10.39 was required but it was not (yet) on ibiblio (this seems
fixed today however...). I then bootstrapped from the last July-based
file which worked but emerge system stopped with some error message
(can't quite remember what it was right now something with shutils I think).
Having done this two times I tried to Install from 'portage-20010730.tar.bz2'
which I had lying around from some earlier experiments. This compiled to the
end but left me in a system missing vital components like grub, 
start-stop-demon etc.... The emerge on grub worked but it kept searching
for /boot/grub/stage1 and returned a "file not found" even after I put the 
file there.(?) But after the reboot I only ended up in a maintenance console
due to the lacking sysVinit tools...
Today I again tried the classical approach which found an abrupt halt again
in the bootstrapping process. gettex was found OK this time but ./configure
complained about an unknown machine type "i685-pc-linux-gnu" ->
there is a typo in the new make.conf in the PIII/Athlon section...
but emerge system then stops complaining about missing makeinfo
somewhere along the way...
Am I doing something completely wrong or is portage in a state which does
not allow a complete build-install right now.
Could my USE flags be the culprit (I remove everything sound-related (no 
card), gnome pcmcia-cs and only include perl, python, tcltk svga and tex
from the stable USE flags. And I use the PIII flags for CHOST/CFLAGS...

 - autofs:   in the startup script in the generation of the pidfile-name
the sed-command 's/\//./' should be changed to 's/\//./g' otherwise 
mountpoints like /something/with/more/than/one/slash is causing problems
since just autofs.something.pid is created but the script then looks for
autofs.sometihng/with/more.... and fails to start.

 - xinetd: in the standard configuration xinetd just puts three lines to the 
syslog complaining about unknown "time-stream" and "time-dgram" and
no more services - exiting, just to be restarted by supervise and the cycle
starts again. Maybe xinetd shouldn't be started automatically since this 
currently just fills the syslog.

 - mozilla: the ebuild builds fine and I can start mozilla from a Konsole in 
KDE and get some mozilla-messages (no direct error message) but then
... nothing. I can just stop the process with ctrl-c and switch to 
konqueror/operea/netscape...

That were the most important things I noticed in these past 10 days.
I am sorry if this is the wrong place to put this and if I'm rather vague
on some of the details but I am currently at home and don't have all
the details handy.

Personally I won't be around for the next 20 days and won't get any answers
until then.
But then I'm sure to try again since I think gentoo is quite promising!

regards

Tibor Rudas

[gentoo-dev] Problems compiling gv

[roberto]

Hi,

I installed Gentoo Linux on my Toshiba Laptop, and it works great. Being a long time fan of OpenBSD and Slackware, Gentoo was just perfect for me, with the best of both worlds.

I´m having some problems, though. I tried ebuilding gv from /usr/portage, and I got the following error:

 make[1]: *** No rule to make target `gv.man', needed by `gv._man'.  Stop.
 make[1]: Leaving directory `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source'
 make: *** [all] Error 2

I get a similar error when trying to compile wmcdplay:

 make: *** No rule to make target `wmcdplay.man', needed by `wmcdplay._man'.  Stop.

Any hints on this?

Thanks in advance,

Roberto

-- 
   ____
  /  o/  Roberto A. F. Almeida                
 <   /|  robertoaf@dealmeida.net                   
 | /\|                     
 |/      
/_\

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 04:02, you wrote:
> Hi,
>
> I installed Gentoo Linux on my Toshiba Laptop, and it works great. Being a
> long time fan of OpenBSD and Slackware, Gentoo was just perfect for me,
> with the best of both worlds.
>
> I´m having some problems, though. I tried ebuilding gv from /usr/portage,
> and I got the following error:
>
>  make[1]: *** No rule to make target `gv.man', needed by `gv._man'.  Stop.
>  make[1]: Leaving directory
> `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: *** [all]
> Error 2
>
> I get a similar error when trying to compile wmcdplay:
>
>  make: *** No rule to make target `wmcdplay.man', needed by
> `wmcdplay._man'.  Stop.
>
> Any hints on this?
>
> Thanks in advance,
>
> Roberto
Hm. There were previous reports of this problem with gv, but then the reports 
stopped, so I assumed the problem was solved. I'll try to look into it today.

About the laptop - what model exactly do you have? I'm asking because I'm 
having some trouble with a Satellite 3000-400 and Buzzard's utils.


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 04:02, you wrote:
> Hi,
>
> I installed Gentoo Linux on my Toshiba Laptop, and it works great. Being a
> long time fan of OpenBSD and Slackware, Gentoo was just perfect for me,
> with the best of both worlds.
>
> I´m having some problems, though. I tried ebuilding gv from /usr/portage,
> and I got the following error:
>
>  make[1]: *** No rule to make target `gv.man', needed by `gv._man'.  Stop.
>  make[1]: Leaving directory
> `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: *** [all]
> Error 2
>
> I get a similar error when trying to compile wmcdplay:
>
>  make: *** No rule to make target `wmcdplay.man', needed by
> `wmcdplay._man'.  Stop.
>
> Any hints on this?
>
> Thanks in advance,
>
> Roberto
OK, I've changed the gv ebuild, though it's rather a guess, but it's the only 
thing I can think of.
If that doesn't help after rsync, could you try to extract and install the gv 
sources yourself, and see if that works? 
A final question: after the make error, emerge shuold say it failed to run 
something - what's that something? I want to know if it failed to compile or 
to install.


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Problems compiling gv

[roberto]

Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
> OK, I've changed the gv ebuild, though it's rather a guess, but it's the only 
> thing I can think of.
> If that doesn't help after rsync, could you try to extract and install the gv 
> sources yourself, and see if that works? 
> A final question: after the make error, emerge shuold say it failed to run 
> something - what's that something? I want to know if it failed to compile or 
> to install.

How do I do a clean rsync?

   bash-2.04# emerge --clean rsync
   !!! Error: --clean is an invalid option.

   bash-2.04# emerge rsync clean
   !!! Error: clean does not exist or is an invalid command-line option.

Ok, I did a simple emerge rsync. Same error when emerging gv:

   make[1]: *** No rule to make target `gv.man', needed by `gv._man'.  Stop.
   make[1]: Leaving directory `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source'
   make: *** [all] Error 2

   !!! ERROR: the make command did not complete successfully.
   !!! ("make")
   !!! Since this is a critical task, ebuild will be stopped.

   !!! emerge aborting on  /usr/portage/app-text/gv/gv-3.5.8.ebuild .

I downloaded the sources with ebuild gv fetch, and got the same error when compiling.

Thanks,

Roberto

-- 
   ____
  /  o/  Roberto A. F. Almeida                
 <   /|  robertoaf@dealmeida.net                   
 | /\|                     
 |/      
/_\

[gentoo-dev] Toshiba laptop (was: Problems compiling gv)

[roberto]

Dan Armak escreveu (Wed, Aug 08, 2001 at 09:58:42AM +0300):
> About the laptop - what model exactly do you have? I'm asking because I'm 
> having some trouble with a Satellite 3000-400 and Buzzard's utils.

I have a Satellite 2250 CDT. The only util that works for me is the fan control. Too bad... I have e-mailed him, but never got any response.

Regards,

Roberto

-- 
   ____
  /  o/  Roberto A. F. Almeida                
 <   /|  robertoaf@dealmeida.net                   
 | /\|                     
 |/      
/_\

Re: [gentoo-dev] Toshiba laptop (was: Problems compiling gv)

[Dan Armak]

On Wednesday 08 August 2001 17:53, you wrote:
> Dan Armak escreveu (Wed, Aug 08, 2001 at 09:58:42AM +0300):
> > About the laptop - what model exactly do you have? I'm asking because I'm
> > having some trouble with a Satellite 3000-400 and Buzzard's utils.
>
> I have a Satellite 2250 CDT. The only util that works for me is the fan
> control. Too bad... I have e-mailed him, but never got any response.
>
I'm having generic problems - all utils say my model isn't supported, but the 
kernel module wroks. And I thought there was no use writing Buzzard because 
he wouldn't answer :-)


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 17:32, you wrote:
> Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
> > OK, I've changed the gv ebuild, though it's rather a guess, but it's the
> > only thing I can think of.
> > If that doesn't help after rsync, could you try to extract and install
> > the gv sources yourself, and see if that works?
> > A final question: after the make error, emerge shuold say it failed to
> > run something - what's that something? I want to know if it failed to
> > compile or to install.
>
> How do I do a clean rsync?
There's no such thing. Did I mention such a thing?

>
>    bash-2.04# emerge --clean rsync
>    !!! Error: --clean is an invalid option.
>
>    bash-2.04# emerge rsync clean
>    !!! Error: clean does not exist or is an invalid command-line option.
>
> Ok, I did a simple emerge rsync. Same error when emerging gv:
>
>    make[1]: *** No rule to make target `gv.man', needed by `gv._man'. 
> Stop. make[1]: Leaving directory
> `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: *** [all]
> Error 2
>
>    !!! ERROR: the make command did not complete successfully.
>    !!! ("make")
>    !!! Since this is a critical task, ebuild will be stopped.
>
>    !!! emerge aborting on  /usr/portage/app-text/gv/gv-3.5.8.ebuild .
>
> I downloaded the sources with ebuild gv fetch, and got the same error when
> compiling.
>
I didn't really expect the problem to be in the ebuild anyway.
This all seems very strange, and I can't do much because I can't recreate the 
problem. If you could send me the entire compile output it might help, and 
then again it might not. I just don't know what to say :-(

One thing I *can* do is simply disable the makefile's operation on the 
manpage. The manpage is actually distibuted pre-compiled (not latex source or 
something), so all the makefile does is add a .1 extension and install it. So 
I'll do that now. Wait a couple of hours after this post, emerge rsync and 
try again.


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 15:31, you wrote:
> On Wednesday 08 August 2001 17:32, you wrote:
> > Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
> > > OK, I've changed the gv ebuild, though it's rather a guess, but it's
> > > the only thing I can think of.
> > > If that doesn't help after rsync, could you try to extract and install
> > > the gv sources yourself, and see if that works?
> > > A final question: after the make error, emerge shuold say it failed to
> > > run something - what's that something? I want to know if it failed to
> > > compile or to install.
> >
> > How do I do a clean rsync?
>
> There's no such thing. Did I mention such a thing?
>
> >    bash-2.04# emerge --clean rsync
> >    !!! Error: --clean is an invalid option.
> >
> >    bash-2.04# emerge rsync clean
> >    !!! Error: clean does not exist or is an invalid command-line option.
> >
> > Ok, I did a simple emerge rsync. Same error when emerging gv:
> >
> >    make[1]: *** No rule to make target `gv.man', needed by `gv._man'.
> > Stop. make[1]: Leaving directory
> > `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: *** [all]
> > Error 2
> >
> >    !!! ERROR: the make command did not complete successfully.
> >    !!! ("make")
> >    !!! Since this is a critical task, ebuild will be stopped.
> >
> >    !!! emerge aborting on  /usr/portage/app-text/gv/gv-3.5.8.ebuild .
> >
> > I downloaded the sources with ebuild gv fetch, and got the same error
> > when compiling.
>
> I didn't really expect the problem to be in the ebuild anyway.
> This all seems very strange, and I can't do much because I can't recreate
> the problem. If you could send me the entire compile output it might help,
> and then again it might not. I just don't know what to say :-(
>
> One thing I *can* do is simply disable the makefile's operation on the
> manpage. The manpage is actually distibuted pre-compiled (not latex source
> or something), so all the makefile does is add a .1 extension and install
> it. So I'll do that now. Wait a couple of hours after this post, emerge
> rsync and try again.

I'm committing to cvs now and it *should* do it. Make sure emerge rsync 
updates the gv ebuild, I don't know how much time it may take for the new 
version to be available via rsync.

In case even this fails, I think there's a slightly newer version of gv and 
I'm going to make an ebuild for that now.


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 16:06, you wrote:
> On Wednesday 08 August 2001 15:31, you wrote:
> > On Wednesday 08 August 2001 17:32, you wrote:
> > > Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
> > > > OK, I've changed the gv ebuild, though it's rather a guess, but it's
> > > > the only thing I can think of.
> > > > If that doesn't help after rsync, could you try to extract and
> > > > install the gv sources yourself, and see if that works?
> > > > A final question: after the make error, emerge shuold say it failed
> > > > to run something - what's that something? I want to know if it failed
> > > > to compile or to install.
> > >
> > > How do I do a clean rsync?
> >
> > There's no such thing. Did I mention such a thing?
> >
> > >    bash-2.04# emerge --clean rsync
> > >    !!! Error: --clean is an invalid option.
> > >
> > >    bash-2.04# emerge rsync clean
> > >    !!! Error: clean does not exist or is an invalid command-line
> > > option.
> > >
> > > Ok, I did a simple emerge rsync. Same error when emerging gv:
> > >
> > >    make[1]: *** No rule to make target `gv.man', needed by `gv._man'.
> > > Stop. make[1]: Leaving directory
> > > `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: ***
> > > [all] Error 2
> > >
> > >    !!! ERROR: the make command did not complete successfully.
> > >    !!! ("make")
> > >    !!! Since this is a critical task, ebuild will be stopped.
> > >
> > >    !!! emerge aborting on  /usr/portage/app-text/gv/gv-3.5.8.ebuild .
> > >
> > > I downloaded the sources with ebuild gv fetch, and got the same error
> > > when compiling.
> >
> > I didn't really expect the problem to be in the ebuild anyway.
> > This all seems very strange, and I can't do much because I can't recreate
> > the problem. If you could send me the entire compile output it might
> > help, and then again it might not. I just don't know what to say :-(
> >
> > One thing I *can* do is simply disable the makefile's operation on the
> > manpage. The manpage is actually distibuted pre-compiled (not latex
> > source or something), so all the makefile does is add a .1 extension and
> > install it. So I'll do that now. Wait a couple of hours after this post,
> > emerge rsync and try again.
>
> I'm committing to cvs now and it *should* do it. Make sure emerge rsync
> updates the gv ebuild, I don't know how much time it may take for the new
> version to be available via rsync.
>
> In case even this fails, I think there's a slightly newer version of gv and
> I'm going to make an ebuild for that now.
 Turns out there isn't a newer version - only rumours. Oh well. But my last 
cvs update might work :-)

Re: [gentoo-dev] Problems compiling gv

[Daniel Robbins]

On Wed, Aug 08, 2001 at 03:31:31PM +0300, Dan Armak wrote:

> > How do I do a clean rsync?
> There's no such thing. Did I mention such a thing?

Yes there is.  If he upgrades Portage, he can then do an "emerge --clean
rsync".  But he needs a recent version of Portage to be able to do it.

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 19:49, you wrote:
> On Wed, Aug 08, 2001 at 03:31:31PM +0300, Dan Armak wrote:
> > > How do I do a clean rsync?
> >
> > There's no such thing. Did I mention such a thing?
>
> Yes there is.  If he upgrades Portage, he can then do an "emerge --clean
> rsync".  But he needs a recent version of Portage to be able to do it.
What does this do beyond remove ebuilds which have been deletd from cvs?


-- 

Dan Armak
Gentoo Linux Developer, Desktop Team
Matan, Israel

Re: [gentoo-dev] Problems compiling gv

[Daniel Robbins]

On Wed, Aug 08, 2001 at 08:26:05PM +0300, Dan Armak wrote:

> > Yes there is.  If he upgrades Portage, he can then do an "emerge --clean
> > rsync".  But he needs a recent version of Portage to be able to do it.
> What does this do beyond remove ebuilds which have been deletd from cvs?

That's all it does.

-- 
Daniel Robbins					<drobbins@gentoo.org>
Chief Architect/President			http://www.gentoo.org 
Gentoo Technologies, Inc.			

Re: [gentoo-dev] Problems compiling gv

[Dan Armak]

On Wednesday 08 August 2001 16:09, you wrote:
> On Wednesday 08 August 2001 16:06, you wrote:
> > On Wednesday 08 August 2001 15:31, you wrote:
> > > On Wednesday 08 August 2001 17:32, you wrote:
> > > > Dan Armak escreveu (Wed, Aug 08, 2001 at 10:45:57AM +0300):
> > > > > OK, I've changed the gv ebuild, though it's rather a guess, but
> > > > > it's the only thing I can think of.
> > > > > If that doesn't help after rsync, could you try to extract and
> > > > > install the gv sources yourself, and see if that works?
> > > > > A final question: after the make error, emerge shuold say it failed
> > > > > to run something - what's that something? I want to know if it
> > > > > failed to compile or to install.
> > > >
> > > > How do I do a clean rsync?
> > >
> > > There's no such thing. Did I mention such a thing?
> > >
> > > >    bash-2.04# emerge --clean rsync
> > > >    !!! Error: --clean is an invalid option.
> > > >
> > > >    bash-2.04# emerge rsync clean
> > > >    !!! Error: clean does not exist or is an invalid command-line
> > > > option.
> > > >
> > > > Ok, I did a simple emerge rsync. Same error when emerging gv:
> > > >
> > > >    make[1]: *** No rule to make target `gv.man', needed by `gv._man'.
> > > > Stop. make[1]: Leaving directory
> > > > `/usr/portage/tmp/portage/gv-3.5.8/work/gv-3.5.8/source' make: ***
> > > > [all] Error 2
> > > >
> > > >    !!! ERROR: the make command did not complete successfully.
> > > >    !!! ("make")
> > > >    !!! Since this is a critical task, ebuild will be stopped.
> > > >
> > > >    !!! emerge aborting on  /usr/portage/app-text/gv/gv-3.5.8.ebuild .
> > > >
> > > > I downloaded the sources with ebuild gv fetch, and got the same error
> > > > when compiling.
> > >
> > > I didn't really expect the problem to be in the ebuild anyway.
> > > This all seems very strange, and I can't do much because I can't
> > > recreate the problem. If you could send me the entire compile output it
> > > might help, and then again it might not. I just don't know what to say
> > > :-(
> > >
> > > One thing I *can* do is simply disable the makefile's operation on the
> > > manpage. The manpage is actually distibuted pre-compiled (not latex
> > > source or something), so all the makefile does is add a .1 extension
> > > and install it. So I'll do that now. Wait a couple of hours after this
> > > post, emerge rsync and try again.
> >
> > I'm committing to cvs now and it *should* do it. Make sure emerge rsync
> > updates the gv ebuild, I don't know how much time it may take for the new
> > version to be available via rsync.
> >
> > In case even this fails, I think there's a slightly newer version of gv
> > and I'm going to make an ebuild for that now.
>
>  Turns out there isn't a newer version - only rumours. Oh well. But my last
> cvs update might work :-)
>
Did it work?

Re: [gentoo-dev] just a little feedback...

[Aron Griffis]

Hello Tibor,

As far as I can tell you haven't gotten many answers to these questions.
I'm new to Gentoo myself but I'll take a shot at some of them.

Tibor Rudas wrote:	[Tue Aug 07 2001, 05:38:42PM EDT]
>  - lately I am experiencing great difficulties in doing an install from the
> 1.0_rc5-r4 build iso image...
> It worked perfectly well on July 27th where I did the emerge rsync
> and the bootstrap. The emerge system followed on July 30th and the
> machine is up and running...
> During the last week however I tried to install an identical machine
> and failed multiple times (and I don't have super bombad racing!).
> At first even the new August-based bootsrap file failed because
> gettext-0.10.39 was required but it was not (yet) on ibiblio (this seems
> fixed today however...). I then bootstrapped from the last July-based
> file which worked but emerge system stopped with some error message
> (can't quite remember what it was right now something with shutils I think).
> Having done this two times I tried to Install from 'portage-20010730.tar.bz2'
> which I had lying around from some earlier experiments. This compiled to the
> end but left me in a system missing vital components like grub, 
> start-stop-demon etc.... The emerge on grub worked but it kept searching
> for /boot/grub/stage1 and returned a "file not found" even after I put the 
> file there.(?) But after the reboot I only ended up in a maintenance console
> due to the lacking sysVinit tools...

I don't know the answers to most of this (probably a lot gets
fixed/broken between bootstrap files).  However I think I know the
answer to the grub problem.

First, note that by default Gentoo doesn't mount the /boot filesystem,
as a precaution to keep it safe from filesystem corruption.  If you want
to to post-boot maintenance on it, you need to "mount /boot".

The next thing is that grub is searching _within_the_/boot_filesystem_
for /boot/grub/stage1.  That means that, relative to the root
filesystem, it actually needs to be installed in /boot/boot/grub/stage1.
I personally think this could be tidier, but it works.  :-)

> Today I again tried the classical approach which found an abrupt halt again
> in the bootstrapping process. gettex was found OK this time but ./configure
> complained about an unknown machine type "i685-pc-linux-gnu" ->
> there is a typo in the new make.conf in the PIII/Athlon section...
> but emerge system then stops complaining about missing makeinfo
> somewhere along the way...

I hope that somebody has fixed this.  I didn't have this problem with
rc5-r4 on Athlon.

> Am I doing something completely wrong or is portage in a state which does
> not allow a complete build-install right now.

I don't know the answer to this either.  Portage is definitely in
a continuing state of flux, but it's been usable for me.

>  - autofs:   in the startup script in the generation of the pidfile-name
> the sed-command 's/\//./' should be changed to 's/\//./g' otherwise 
> mountpoints like /something/with/more/than/one/slash is causing problems
> since just autofs.something.pid is created but the script then looks for
> autofs.sometihng/with/more.... and fails to start.

This has not yet been fixed.  I believe needs to be fixed by somebody on
the Server Team?

> - xinetd: in the standard configuration xinetd just puts three lines
> to the syslog complaining about unknown "time-stream" and "time-dgram"
> and no more services - exiting, just to be restarted by supervise and
> the cycle starts again. Maybe xinetd shouldn't be started
> automatically since this currently just fills the syslog.

The problem here is that xinetd is compiled with ipv6 support, but your
kernel doesn't include ipv6.  There are two parts to solving this
problem:

(1) You need a new xinetd, which I haven't sent to gentoo-ebuild yet,
    but I will sometime today.  There are more problems in xinetd than
    just what you mentioned, which hopefully the new ebuild will fix.

(2) If you want to build with ipv6 enabled, you will need to add it to
    your USE variable.  This is an as-of-yet undocumented use option,
    but the new xinetd ebuild will pay attention to it.

> - mozilla: the ebuild builds fine and I can start mozilla from
> a Konsole in KDE and get some mozilla-messages (no direct error
> message) but then ... nothing. I can just stop the process with ctrl-c
> and switch to konqueror/operea/netscape...

My mozilla build doesn't work either.  I'm of the opinion that there
should be an alternate mozilla ebuild that just uses the prebuilt
binaries (which work!) from mozilla.org.  I may create this if the
Desktop Team doesn't get around to it first.  ;-)

> That were the most important things I noticed in these past 10 days.
> I am sorry if this is the wrong place to put this and if I'm rather vague
> on some of the details but I am currently at home and don't have all
> the details handy.

This is the right place to post these kinds of concerns.  Thanks for
being so detailed!

Aron