Sabayon Linux developers split the Portage sabayon overlay into two new overlays

If you are a Gentoo Linux user who added the sabayon overlay, or if you are a Sabayon Linux user who already uses Portage, note that the developers of Sabayon Linux have just split the overlay into two overlays. One of the overlays (sabayon-distro) contains ebuilds that are specific to the Sabayon Linux distribution and unlikely to be of interest to users of other distributions that use the Portage package manager. The other overlay (sabayon) contains ebuilds that could be of interest to Portage users of other distributions. For example, the package app-misc/sabayon-version will only be of relevance to users of Sabayon Linux, so you’ll only find it in the sabayon-distro overlay, not the sabayon overlay:

# eix sabayon-version
* app-misc/sabayon-version [1]
Available versions: (~)5-r5 (~)7-r1
Homepage: http://www.sabayon.org/
Description: Sabayon System Release virtual package

[1] "sabayon-distro" /var/lib/layman/sabayon-distro

All you need to do in order to cater for this change is the following as root user:

layman -d sabayon
layman -S
layman -a sabayon
layman -a sabayon-distro
eix-update

You only need to add the sabayon-distro overlay if you are a user of Sabayon Linux or want to install any of the distribution-specific ebuilds from it. Of course omit the eix-update command if you do not have the excellent eix utility installed.

From then onwards you can just continue as normal using the usual Portage commands as root user in order to synchronise the main Portage tree and synchronise all the overlays added on your machine:

emerge --sync
layman -S
eix-update

or, if you have an asterisk on its own line in the file /etc/eix-sync.conf then you can replace the above three commands with the following single command:

eix-sync

About Fitzcarraldo
A Linux user with an interest in all things technical.

4 Responses to Sabayon Linux developers split the Portage sabayon overlay into two new overlays

  1. hicks1gb says:

    Thanks for the input.
    I have a problem and was wondering if you could help me.

    I am trying to install the Brother printer drivers in sabayon. I have the overlays.

    http://gpo.zugaina.org/net-print/brother-dcp-j315w-drivers
    brother-mfc-j265w-drivers-1
    Overlay: amielke-overlay (layman)

    http://gpo.zugaina.org/net-print/brother-mfc-j265w-drivers
    brother-dcp-j315w-drivers-1
    Overlay: funtoo (distro)

    in the terminal as root:

    equo install git eix layman
    layman-S
    layman-a funtoo
    Exception: Overlay “funtoo” does not exist.

    layman-a amielke-overlay
    This OK.

    then run:

    eix brother

    * Net-print/brother-mfc-235c-drivers [1]
    Available versions: (~) 1! S
    Homepage: http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_prn.html # DCP-J315W
    Description: Brother DCP-LPR + cupswrapper drivers J315W

    * Net-print/brother-mfc-j265w-drivers [1]
    Available versions: (~) 1! S
    Homepage: http://welcome.solutions.brother.com/bsc/public_s/id/linux/en/download_prn.html # DCP-J315W
    Description: Brother DCP-LPR + cupswrapper drivers J315W

    [1] “amielke-overlay” / var / lib / layman / amielke-overlay

    Found 2 matches.

    But when I try to install the packages net-print/brother-mfc-j265w-drivers and net-print/brother-mfc-235c-drivers:

    equo install net-print/brother-mfc-235c-drivers
    packages have not been found

    and

    equo install net-print/brother-mfc-j265w-drivers
    not find the packages.

    Can you tell I’m doing wrong?

    Thanks in advance….

    • Fitzcarraldo says:

      You are mixing apples and oranges. You used the Portage layman command to add a 3rd-party overlay and download its ebuilds. ebuilds are scripts used by the Portage package manager, not the Sabayon Linux package manager Entropy. Those two packages do not exist in Entropy. Therefore you need to use Portage to install the packages by using the ebuilds:

      emerge -1v brother-mfc-235c-drivers
      emerge -1v brother-mfc-j265w-drivers

      If you did not already do it, make sure you have done:

      emerge --sync

      before, so that your installation is synchronised with the current ebuilds in the main Portage tree.

Leave a comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.