NikosAlexandris

Ok there's quite a few outdated documents and command warnings that cause problems here.
 
First of, emerge <ebuildname>.ebuild from the current overlay directory tends to work. I generally don't use it since the ebuild
tool allows you to install a package just like emerge does, but it does this by going through different stages.
 
Let's start with the prerequisite: The manifest file.
 
You don't have to run ebuild *.ebuild manifest, just run ebuild <ebuildname>.ebuild manifest, which will generate a manifest for all ebuilds in the current directory. There's also repoman, which Gentoo uses, and which can create manifests as well: repoman manifest will create manifest entries for all ebuilds that don't have one already.
 
I highly recommend reading "man ebuild" on how to use the ebuild tool. It will make debugging ebuild problems a lot easier. A basic way to install a custom ebuild using the ebuild tool can be done like this, if the manifest is correct:
ebuild gdal-2.0.3.ebuild fetch (downloads the package and verifies that its integrity using the manifest file) ebuild gdal-2.0.3.ebuild unpack (downloads the package and untars it into /var/tmp/portage/sci-libs/gdal-2.0.3.ebuild) ebuild gdal-2.0.3.ebuild prepare (applies any patches and prepares the ebuild) ebuild gdal-2.0.3.ebuild configure (runs the configure script of autotools) ebuild gdal-2.0.3.ebuild compile (compiles the packages) ebuild gdal-2.0.3.ebuild install (this will install the package into a sandbox, that is, into /var/tmp/portage/sci-libs/gdal-2.0.3/image folder) ebuild gda1 qmerge (install the package into the system. At this point, the whole process is completed and is equivalent to running emerge) Some phases also include others. Typically, you'll skip the fetch and configure phase, they are included in the other commands (unpack and compile). I haven't listed some of the phases due to brevity. This is still a very verbose way to install an ebuild, and a bit tedious.  A simpler way to use the ebuild tool is to run:
ebuild <ebuildname>.ebuild merge ,which is equivalent to running: emerge <ebuildname>.ebuild.
 
Consider reading both man ebuild (for the tool) and man 5 ebuild (for the ebuild syntax). They're the most accurate documents at the moment.
 
It seems somebody masked the newer versions of gdal for some reason. This needs further investigation. It might be a malformed mask and you should add an entry to package.unmask for the time being:
>=sci-libs/gdal-2.0.3
 
Drop by on IRC sometime and I'll be glad to assist you with any questions. Just ping me (bhenc) and I'll help you get started with the ebuilds. If you're unfamiliar with IRC, the www.funtoo.org/Getting_Help  page might be a good place to start.
 
Happy hacking!

Just closing this topic. All works fine.

It is unfortunate that boot has been unsuccessful. Comments left on the Talk page.

Open /usr/bin/euse as root in text editor.
Comment line 723,add bold text and save.
#eval $(portageq envvar -v PORTDIR)
: ${PORTDIR="$(portageq get_repo_path $(portageq envvar EROOT) gentoo)"}
 
get_portdir() { # Use a subshell so we don't have to protect the variables in # the current scope ( #eval $(portageq envvar -v PORTDIR) : ${PORTDIR="$(portageq get_repo_path $(portageq envvar EROOT) gentoo)"} echo "${PORTDIR}" ) } # }}} Reference: https://goo.gl/WXOGhM

I wish I had the graphic talent to provide you with something worthy.  I did a search for appropriate symbols for systemd but this is all I could find...
 

 
Credit: http://www.codekid.net/index.php?itemid=2026

Hi Nikos, yes I've read your above post -> my message is don't use bliss-boot, just create your initrd with bliss-initramfs edit /etc/boot.conf. Use Daniels boot-update and be happy;-)
I've tried several times to get a clean boot with bliss-boot - never had succes so my advice is to do it "simpler"
cu Peje
p.s:
this enty forces the import of the pool
params += dozfs=force

Hi I just use bliss-initramfs, edit /etc/boot.conf and run boot-update
sample:
kernel and intird are stored in /boot
Its simpler like this... cu peje

Have you tried booting with System Rescue CD, 'chrooting' into your install and exporting the zpool from within the chroot?

Try the following...
emerge --unmerge udev && emerge --oneshot eudev && emerge --unmerge upower && emerge --oneshot sys-power/upower-pm-utils That should fix the udev problems... I was having the same issue trying to install cinnamon.
 
Just make sure that it finishes before you reboot otherwise your system will be broken. udev and upower are both system packages that are nessesary to boot correctly.
 
eudev and upower-pm-utils replace udev and upower respectivly.
 
Hope that this helps.
 
P.S. You will probably have to run the following after the above to fix linked libraries but portage should tell you that.
emerge @preserved-rebuild

I don't believe they're in Funtoo/Gentoo.  The overlays I found seem to be externally maintained in layman.  But, I'm pretty new to this whole process, so perhaps that qualifies them as being included.
 
I'm not sure how well maintained the others are, but I use Plex everyday and maintain my installation quite voraciously.
 
Here's my github repo:
 
https://github.com/Ghent/funtoo-plex

Alrighty, ticket opened on bugs. :)
 
http://bugs.funtoo.org/browse/FL-1266

via bugs.funtoo.org

Okay, I have now enabled this globally :)