drobbins

Sorry for not catching this sooner. This info has been migrated into the funtoo profiles themselves, so it is no longer needed in metro.

I updated the search settings so 3-word search terms should be okay.

Have someone do an emerge --quickpkg portage for you and install the resultant tarball by extracting to /:
 
# tar xpf portage.tbz2 -C /

Sure, here's the info. The way the variables in /etc/make.conf are "merged" into the defaults in the profile is a fairly complex process, but...
 
There is really no difference for the *FLAGS, since there is only a very generic default.
 
You want to make sure you use the FOO="${FOO} blah" format when you have lines earlier in the same file that define FOO. If you do not, they you will overwrite your earlier settings. If you use FOO="${FOO} blah", then you will *add* blah to your existing settings you defined earlier in the same file.
 
 
How variables are handled in /etc/make.conf is interesting -- there are two types of variables. Regular variables, and "incrementals". The incrementals are:
 
"USE", "USE_EXPAND", "USE_EXPAND_HIDDEN", "FEATURES", "ACCEPT_KEYWORDS", "CONFIG_PROTECT_MASK", "CONFIG_PROTECT", "IUSE_IMPLICIT", "PRELINK_PATH", "PRELINK_PATH_MASK", "PROFILE_ONLY_VARIABLES",  "USE_EXPAND_IMPLICIT", "USE_EXPAND_UNPREFIXED"   The most common incremental is USE. What makes use incremental? "Incremental" means that if you set this in /etc/make.conf:   USE="foo"   ... then "foo" will be *added* to your existing USE setting. This makes it incremental.   To totally wipe your USE, you must do:   USE="-* foo"   If something is NOT an incremental, then you can wipe the variable by going:   FOO="bar"   and to preserve existing settings for non-incremental, if there are any, you must do:   FOO="${FOO} bar"   CFLAGS, etc. are non-incremental, but there are just basic defaults of typically "-O2 -pipe", so generally people just override.   -Daniel

The tree *was* broken. I have added many ebuild updates to address this.
 
What is happening is that Gentoo is updating some ebuilds to be able to build 32-bit binaries on 64-bit systems in order to get rid of the emul-linux-x86 packages. This is resulting in lots of ebuilds in Gentoo depending on these new USE variables. The ebuilds in Funtoo need to be updated to provide 32-bit builds and thus these USE variables. This is impacting a lot of "core" ebuilds, which of course are the ones that we tend to have forked in Funtoo.
 
Jean-Francis is going to be testing my updates, and we should be pretty much on top of this issue from now on. However, as Gentoo transitions away from emul-linux-86, it is possible that you may see very similar build failures (missing abi_x86_32 USE flags in ebuilds) -- just report them on bugs.funtoo.org and we will get them fixed as soon as possible.

For now, contact me privately and I can reset your password.
 
-Daniel

I've gone ahead and set it up. Try it out and let me know what you think.

We are not officially supporting systemd in Funtoo Linux "proper", which means that we will be stuck at GNOME 3.6 for a while.
 
I am planning to launch a project called FOAM (Funtoo Of Another Mother) which supports systemd and GNOME 3.12+. This will be a Funtoo-based system that uses systemd. But it won't be considered "Funtoo.".

Okay, I have now enabled this globally :)

Did you install Chromium as described here, with chrome-binary-plugins: Funtoo Linux Web Browsers: Chromium ?