Wasn't someone saying it'd be unmasked by tomorrow? (end of the week?)kirillrdy wrote:Should be maskedrush_ad wrote:just checked gentoo-portage
they have listed gnome-2.14 now. masked though.for a while at least.
Wasn't someone saying it'd be unmasked by tomorrow? (end of the week?)kirillrdy wrote:Should be maskedrush_ad wrote:just checked gentoo-portage
they have listed gnome-2.14 now. masked though.for a while at least.

I dont know, Actually ofcourse all of us would like to see it unmasked sooninsh. We'll seeprotex wrote:Wasn't someone saying it'd be unmasked by tomorrow? (end of the week?)kirillrdy wrote:Should be maskedrush_ad wrote:just checked gentoo-portage
they have listed gnome-2.14 now. masked though.for a while at least.


I always keep a separate gentoo for breakagelex82 wrote:I guess I'm going to wait a little bit more... maybe when it hits testing.
It's not difficult but the line "unmasking this packages may break your system" sounds bad to me!

Actually I already emerged gnome-terminal-2.14, couse I head its should be super fast.lex82 wrote:Let me know if everything is ok...kirillrdy wrote:But I'll try 2.14 tomorrow,
Code: Select all
pkg_setup() {
# Compositor is too unreliable
G2CONF="$(use_enable xinerama) --disable-compositor"
}
every thing is here : http://gentoo-wiki.com/HOWTO_XGL and here : http://forums.gentoo.org/viewtopic-t-442410.htmlolger901 wrote:How do you enable XGL, do you need xorg-7.0 for it? Do the ati-drivers work with XGL?
Someone have post a way to modify the ebuild to enable compistor with USE. But you can also modify the ebuild : raplce --disable-compositor by --enable-compositor. But you should have libXcomposite et libXdamage installed.Rikz wrote:Does somebody know, what about metacity compositor?
According to metacity-2.14.1.ebuild it is permanently off:Code: Select all
pkg_setup() { # Compositor is too unreliable G2CONF="$(use_enable xinerama) --disable-compositor" }
But as far as I know, it could be easily disabled (and is disabled by default) via gconf. Maybe it is time to add a USE flag for compositor?
Code: Select all
/usr/lib/gcc/i686-pc-linux-gnu/3.4.5/../../../../i686-pc-linux-gnu/bin/ld: .libs/nautilus: hidden symbol `__popcountsi2' in /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/libgcc.a(_popcountsi2.oS) is referenced by DSO
/usr/lib/gcc/i686-pc-linux-gnu/3.4.5/../../../../i686-pc-linux-gnu/bin/ld: final link failed: Nonrepresentable section on output
collect2: ld returned 1 exit status
make[4]: *** [nautilus] Error 1
make[4]: Leaving directory `/var/tmp/portage/nautilus-2.14.0/work/nautilus-2.14.0/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/nautilus-2.14.0/work/nautilus-2.14.0/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/nautilus-2.14.0/work/nautilus-2.14.0/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/nautilus-2.14.0/work/nautilus-2.14.0'
make: *** [all] Error 2
!!! ERROR: gnome-base/nautilus-2.14.0 failed.
Call stack:
ebuild.sh, line 1565: Called dyn_compile
ebuild.sh, line 974: Called src_compile
ebuild.sh, line 1280: Called gnome2_src_compile
!!! compile failure
!!! If you need support, post the topmost build error, and the call stack if relevant.
Well... maybe too much unstable packages?thasheep wrote:I've emerged nautilus - and almost everything in the gnome metapackage (I left out a few things that I don't like and evince because I couldn't compile poppler).
That's all great but none of it is working. It might have something to do with my gcc - I'm using gcc-4.1 and maybe a couple too many cflags. Everything that's built on glibc is exiting with a segfault

I have no idea why it is masked. I guess that there's some problem with mono in this arch but I didn't find it.Devport wrote:Thanks, that did it. But why is it masked for this arch in this additional way ?!-ArTo- wrote:If you've amd64 add "-mono" to "/etc/portage/profile/use.mask"Devport wrote:gmime 2.1.19 does not show mono use flag for me even though its in the ebuild ?