Re: [gentoo-dev] glibc ebuilds

["Tod M. Neidt" <tneidt@fidnet.com>]

Hi!

> Is there any fundamentally good reason why you don't check for the
> presence of /tmp/.X?-lock, which XFree itself checks for to determine if
> an existing X is running ?
> 

Yes... my blatant ignorance of X! :)  You are right /tmp/.X?-lock is
the way to check for X running.  As you can tell, I have no qualms about
baring my ass in public.  That said, sheild your eyes.

I recently, updated several gnome-apps to the current versions (I'm
composing this in evo 0.99, thanks hallski!).  While updating, I ran
into a couple situations where I hosed my gnome-session out from under
myself.  Normally, you can safely emerge a gnome-app while running a
gnome-session.  However, if the app emerge triggers an update of one of
the underlying libs through a dependency you will promptly shoot
yourself in the foot.  This happened to me when imlib and gdk-pixbuf
were updated while emerging the new evolution and gnumeric.  It would be
nice if *critical* gnome-libs ebuilds would check to make sure you are
not running a gnome-session before merging, and ask you to drop down
into console mode to do the merge.  

I assume that a kde or other desktop environments would have similar
situations.

tod

ps.  I tried duplicating the glibc emerge failure that was reported, but
didn't see.  However, the error was reported after a emerge system, but
I checked for it with ebuild glibc unpack compile install.  Although I
am sure I would have hosed my self if qmerged, the build and install did
not fail.