shaman

I'm not satisfied for the presence of debian-source in Funtoo.
# emerge --deselect debian-sources && emerge -C debian-sources Then
# echo "sys-kernel/debian-sources">>/etc/portage/package.mask # euse -E experimental -p sys-kernel/gentoo-sources # emerge gentoo-sources genkernel Then open /etc/genkernel.conf if you want to change some parameters. And to set the "MAKEOPTS" variable as n?threads+1; then # genkernel --menuconfig all ( at first if you've more then one sys-kernel*-sources, use :
# eselect kernel list # eselect kernel set X (where X is the number relative at the kernel that You want to compile).
 
Ciao :)

"Important
Right now, the -1 option is required to not add our @kernel set to world-sets. This allows you to emerge it independently from @world. If you forget to use this option, edit /var/lib/portage/world-sets and remove the @kernel line. This will prevent kernel updates from being included in @world updates."
- http://www.funtoo.org/Funtoo_Linux_Installation
 
 
anyways /var/lib/portage/world needs any sys-kernel lines removed to not fetch kernels at world updates ;-)

Lots of news here -- enjoy!
 
http://www.funtoo.org/News:Newsletter,_Volume_1
 
-Daniel

So far my experience has been, you can use /usr/local/portage, or an overlay of your own, I would recommend the overlay, since you can make changes to it as normal user. there's an skeleton overlay uploaded for funtoo in github, you can start from that.
 
Make the directory structure for the package you wan to test in your overlay dir:

$ mkdir -p ${OVERLAY_DIR}/cat/pkg/ # Edit your ebuild: $ $EDITOR ${OVERLAY_DIR}/cat/pkg/pkg-0.0.ebuild # generate a Manifest $ ebuild ${OVERLAY_DIR}/cat/pkg/pkg-0.0.ebuild manifest Add your overlay via making a overlay.xml file in /etc/layman/overlays/ (this is documented in the layman manual) or adding to your make.conf
PORTDIR_OVERLAY="${PORTDIR_OVERLAY} $YOUR_OVERLAY_DIR" If you don't have the package installed already or are adding new dependencies you can do:
$ sudo emerge --onlydeps '=cat/pkg-0.0' and then you can test your ebuild step by step using the 'ebuild' command, I try before merging anything I edit, generating a package, this means all the build process is made except actually getting the package in your filesystem, you can inspect the tarball generated to see everything looks right and then merge.
$ sudo ebuild ${OVERLAY_DIR}/cat/pkg/pkg-0.0.ebuild package That said you should read first and mainly refer to the gentoo dev documentation.[1] or 'emerge -av devmanual' 
[1] http://devmanual.gentoo.org/index.html

You forgot to tell them to remove/rename the existing portage directory first. :)
 
But this issue has been propping up quite a lot lately and it should have a simpler fix. I will be looking into this and if I find a proper answer it will be documented on FL-1429, otherwise a clean reinstall of the portage tree is the way to go.