Sandro

Are you asking how would you know if there's a new prime branch of a kit?  I think at the moment that's going to have to be user driven, you *want* to use a certain version and so you'll check if there's a prime kit for it.  Otherwise, if you stick to default you'll just roll with funtoo whenever it changes.
 
It might also be a good idea for ego to check /etc/ego.conf for obsolete pinned kits, so the user can take action to update.  Not sure if that's a feature (or planned) yet, but I don't think there's many new prime branches yet anyways.  The only one I've looked at so far is python-3.6.

Think the transition has been more difficult and piecemeal than would be ideal.  I think once the transition is complete and all the tools are in place Funtoo has the potential to be a much better distro for the average user than it has been.  Kits have the potential to reduce the number of breaking changes that get through to users.

if you use only prime branch, then use "ego sync"
if you have some of kits with other branches enabled (such as master), do not use "ego sync"
to update kits with other branches enabled, use following sequence of commands:
 
cd /var/git/meta-repo
git pull
git submodule update
chown -R portage:portage /var/git/meta-repo
 
eix-sync does not update meta-repo, neither default branches nor any other branches. after manually updating meta-repo or if you use default branches and ego sync, you can use eix-update.

Remove  early_ucode.cpio  from your bootloader configuration.
 
https://wiki.gentoo.org/wiki/Intel_microcode

[ot]
@Cardinal: Never abandon us ... your knowledge is too precious. With so much esteem Sandro [/ot]   :)

The command that you quote only lists metadata about the installed gentoo-sources packages.
 
For equery it sounds like you want to use the 'list' module to list packages.

equery l -op gentoo-sources The overlay and portage (-op) options are required to list packages other than those that you have installed.

Arch is "near to *too".
But by default you've precompiled packages.
With *too Portage will compilete your ebuilds (packages)
 
I know that is possible to use aur or yaourt (time ago) to compile from sources.
 
I think that about source-based distributions, *too then the "Portage" is the more genial & eclectic.
 
@McQ have you ever used the subarch "native_64" ?
 
For me ... simply the best cause can be differencies. I make an example about core2 processors:
core2 I generation uses up to SSSE3 SIMD; but if you have a 2nd generation ("Penryn") core2 cpu you will have also the SSE4.1
 
Then i think that only the "native" can optimize perfectly.
 
Another example: i've a core i7 4771 (Haswell) but there are differencies from a 4770K (unlocked) and 4771 (locked but 3 instructions more for Vt technology)
 
to see the flags passed ... open a terminal then digit:
echo 'int main(){return 0;}' > test.c && gcc -v -Q -march=native -O2 test.c -o test && rm test.c test Then open a 2nd terminal and try 
echo 'int main(){return 0;}' > test.c && gcc -v -Q -march=westmere -O2 test.c -o test && rm test.c test Compares the 2 terminals and take a look if there are differencies or not.
 
I use this method
 
I wish not to have bored you :)

Thanks the last option works like charm!!
kali ~ # emerge --sync >>> Syncing repository 'gentoo' into '/usr/portage'... /usr/bin/git pull Already up-to-date. === Sync completed for gentoo q: Updating ebuild cache in /usr/portage ... q: Finished 39297 entries in 0.136935 seconds kali ~ #

I've decided to keep the forums.

# emerge --deselect net-misc/networkmanager # euse -E networkmanager # emerge -DNuav world Then, when terminated Tell us about # emerge -cp To have a more "brilliant & claned" /var/lib/portage/world _'_
 
Usually, with * too (Gentoo & Funtoo), the best thing is that only the "main" softwares are present in the / var / lib / portage / world file. What you want. If in the use flags you enter "networkmanager", it will be installed without "weighing" @world. I think it takes time to give a check and cleaning in /etc/portage/package.[accept_keywords, use, mask, unmask]. In this way it will be easier to manage and ... if need be "replay your Funtoo in my very intuitive. Do not include softwares dependencies in world files. In this way Portage will work better: P If you need to compile or recompile a dependency, use the "emerge --oneshot" (= emerge -1)

dev-util/nvidia-cuda-toolkit-6.5.19-r1.ebuild
RDEPEND="${DEPEND}
<sys-devel/gcc-4.9[cxx]

Hello, Sandro!
 
That good that I helped!
It may not be possible to have master and prime in same folder. You tried to put each one in one folder? So:
 
#mkdir /usr/portage-kits
#cd /usr/portage-kits/
#git clone -b master git://github.com/funtoo/xorg-kit.git
#mv xorg-kit xorg-kit-master
#mkdir /usr/portage-kits/xorg-kit-prime
 
And to have this in folder /etc/portage/repos.conf:
 
- file gentoo:   [DEFAULT] main-repo = gentoo   [gentoo] location = /usr/portage sync-type = git sync-uri = git://github.com/funtoo/ports-2017.git auto-sync = yes   - file xorg-kit-master:   [xorg-kit-master] location = /usr/portage-kits/xorg-kit-master sync-type = git sync-uri = git://github.com/funtoo/master/xorg-kit.git auto-sync = yes   - file xorg-kit-prime:   [xorg-kit-prime] location = /usr/portage-kits/xorg-kit-prime sync-type = git sync-uri = git://github.com/funtoo/master/xorg-kit.git auto-sync = yes  
Then you do: eix-sync
 
Maybe this is the solution final!

its not able to run from root, because root is not in portage group by default
to fix this you need to add root into portage group by:
gpasswd -a root portage
and it will work

Correcting:
 
#rm -R /usr/portage-kits/xorg-kit #cd /usr/portage-kits/ #git clone -b master git://github.com/funtoo/xorg-kit.git

If I do 'eix xorg-server' I have:
 
x11-base/xorg-server [1]      Available versions:  1.12.4-r7(0/1.12.4) 1.15.2-r4(0/1.15.2) 1.18.4(0/1.18.4) 1.19.2(0/1.19.2) (~)1.19.3(0/1.19.3) **9999(0/9999) {debug dmx doc glamor ipv6 kdrive libressl minimal nptl selinux static-libs +suid systemd tslib +udev unwind wayland xephyr xnest xorg xvfb}      Installed versions:  1.19.3(0/1.19.3)(14:31:00 03-04-2017)(dmx ipv6 kdrive suid udev xorg -debug -doc -glamor -libressl -minimal -selinux -static-libs -systemd -tslib -unwind -wayland -xephyr -xnest -xvfb)      Homepage:            https://www.x.org/wiki/      Description:         X.Org X servers   [1] "xorg-kit" /usr/portage-kits/xorg-kit

Hello, Sandro!
 
I made it:
 
#mkdir /usr/portage-kits/
#cd /usr/portage-kits/
#git clone -b master git://github.com/funtoo/xorg-kit.git
 
And I have this in my folder /etc/portage/repos.conf:
 
- file gentoo:
 
[DEFAULT] main-repo = gentoo   [gentoo] location = /usr/portage-tree sync-type = git sync-uri = git://github.com/funtoo/ports-2017.git auto-sync = yes   - file xorg-kit:   [xorg-kit] location = /usr/portage-kits/xorg-kit sync-type = git sync-uri = git://github.com/funtoo/master/xorg-kit.git auto-sync = yes   And I did several times "emerge --sync" and "eix-sync" without any error! It's OK for me!

cd xorg-kit List all available branches :
rj@funtoo ~/xorg-kit $ git branch -a * master   remotes/origin/1.17-prime   remotes/origin/HEAD -> origin/master   remotes/origin/gentoo-1.17-snap   remotes/origin/gentoo-1.19-snap   
 
New Ports-2017 tree and Kits
 
For xorg-kit, you will want to check out the 1.17-prime branch. You can keep ports-2017 on the master branch.
1.17-prime is a branch that contains a curated snapshot of xorg 1.17. We have grabbed a snapshot of xorg from Gentoo that we have found particularly stable, and will be adding security backports, bug fixes and feature enhancements -- but without bumping versions of ebuilds. This is equivalent to an 'enterprise grade' version of xorg. If you need to run xorg and just have it work, all the time, and not have it break, you can know that sticking with the 1.17-prime branch will greatly increase your likelihood of this happening. It is what 1.17-prime is designed for. Note the "-prime" extension, which is our way of saying "this is the good stuff" -- the prime cuts of Larry the Cow  ;) 1.17-prime's functionality and hardware support should continue to remain constant -- so that if it works well on your laptop, you can have very good confidence that you can reload your laptop using 1.17-prime and it will continue to work well into the future.
rj@funtoo ~/xorg-kit $ git checkout 1.17-prime Branch 1.17-prime set up to track remote branch 1.17-prime from origin. Switched to a new branch '1.17-prime' rj@funtoo ~/xorg-kit $ git branch * 1.17-prime master Bleeding-edge users will want to use the master branch to get access to all the latest Gentoo goodies:
rj@funtoo ~/xorg-kit $ git checkout master Switched to branch 'master' Your branch is up-to-date with 'origin/master'. rj@funtoo ~/xorg-kit $ git branch 1.17-prime * master

Very Happy for this choice.
Magic Daniel .... You're Our Hyper-Master :) :P
God Bless You :)

Gentoo's Bugzilla ? Bug 589130 app-portage/gentoolkit-0.3.2-r1: revdep-rebuild: Could not save cache: unicode argument expected, got 'str'
Fixed in gentoolkit-0.3.3

Ok ... Great Dear Oleg .... Thanks to You for explanation :)
You're ever greet \o/.
 
Thx Very much !!! :)

I might add that ... in case of problems with "timing", there are more "ways" :)
e.g. :
# Cd /usr/portage && git reset --hard && emerge --sync or drastically
# rm -rf /usr/portage && emerge --sync Clearly occur before the connection is available .. otherwise be necessary to re-perform the chroot in this case (II) _'_

So, I masked the version app-office/ledger-3.1.1 and install 3.1-r1. It compiled without any problem!! It downgrades the dependencies: dev-libs/boost-1.62 and dev-util/boost-build-1.62 to 1.56. Perhaps it has to do with the linking error at the end of the built..just a guess..
Should I fill a bug about this? 

so you can add the variable : ABI_X86="32 64" 

http://www.funtoo.org/News:Python_Updater_Deprecation
 
My ~amd system:
 PYTHON_SINGLE_TARGET="python3_4" PYTHON_TARGETS="python2_7 python3_4"
Available Python interpreters:
  [1]   python2.7
  [2]   python3.4 *
 

hello,
 
using gcc-6.2 for quite some time now, originally from hardened overlay and no problems so far, except some packages needed extra gcc-6.2 patching.
 
my new xeon system purrs like a kitten  :D
 
greetings