Bitcetera Overlay
Description
This is a development overlay which contains a few ebuilds for Gentoo Linux we are working on. All of them are in a flux and not supported, you use them at your own risk!
Some of the ebuilds are mirrored to other overlays or the main tree once they are tested.
Our hardware is based on amd64 and we can't test the ebuilds on other architectures. Please drop us a line with your observations.
Available Development Ebuilds
| Ebuild | Description |
|---|---|
| app-admin/eselect-ruby | Manages multiple Ruby versions (includes format-executable patch and USE flag). |
| app-misc/heyu | Utility to control and program CM11A, CM17A and CM12U X10 interfaces (more). |
| dev-lang/ruby | An object-oriented scripting language (more). |
| dev-ruby/trollop | Commandline option parser for Ruby (more). |
| mail-filter/postwhite | Policy server for Postfix MTA which filters incoming emails based on per recipient whitelists managed by an email frontend (more). |
| net-firewall/vuurmuur | Easy to use console frontend for iptables firewalling (more). |
| net-libs/libvuurmuur | Libraries and shared components for Vuurmuur (more). |
| net-voip/yate | Next-generation telephony engine or "Asterisk on steroids" (more). |
| net-voip/yate-svn | Next-generation telephony engine or "Asterisk on steroids" from Subversion repository (more). |
| sys-auth/otpw | Generator and PAM module for one-time password lists with a user-defined static password prefix (more). |
Installation
One-time Preparation
The Bitcetera overlay is available from a Git repository. Thus if necessary install git:
emerge -av dev-util/git
If necessary install layman which will manage overlays for you:
emerge -av layman
Edit the overlay line in /etc/layman/layman.cfg to look something like:
overlays: http://www.gentoo.org/proj/en/overlays/layman-global.txt http://github.com/svoop/bitcetera-overlay/raw/master/layman.xml
Add the overlay and retrieve the actual overlay data:
layman -L layman -a bitcetera
Emerge
Emerging an ebuild from overlays is done the same way as regular ebuilds. Replace {EBUILD} with the actual name (i.e. app-misc/heyu):
layman -S
emerge -av {EBUILD}
This will fail if your architecture is not listed as stable above. You may override this and give it a shot nonetheless. If you are - let's say - on ppc and would like to try emerging an ebuild with keyword ~amd64, you have to add the following line to /etc/portage/package.keywords:
{EBUILD} ~amd64