HForge's Gentoo Overlay

HForge.org has an overlay which provides differents Gentoo ebuilds.
Theses ebuilds are mainly dependances of itools or ikaaro projects.

Ebuilds

dev-libs/hlib

This library provides some convenience tools for developpers.

dev-python/itools (0.60.2)

Itools is a Python library which provides a wide range of capabilities.

dev-python/lpod-python (0.9.0)

             Python API around the OpenDocument Format standard

             ( see: http://lpod-project.org )

media-gfx/pngquant (1.0)

Pngquant is a command-line utility to quantize and dither 32-bit RGBA PNGs down to 8-bit (or smaller) RGBA-palette PNGs,
 usually with a significant reduction in file size.

How to use these Overlay (using layman < 1.3.0)

• Install layman :
  

  # emerge -av layman

• Edit section 'overlays' in /etc/layman/layman.cfg and add :
  

  http://overlay.hforge.org/list.xml

• Fetch new list :
  

  # layman -F

• Add hforge-overlay to layman :
  

  # layman -a hforge-overlay

• Edit /etc/make.conf and add :
  

  source /usr/portage/layman/make.conf

• Synchronize overlays list :
  

  # layman -S

You should be able to use HForge's overlay.

Note:

If you are using a version of layman >= 1.3.0 (masked), you should change your configuration according to the new storage location. This is the content of the news available by 'eselect news read' way :

2010-02-28-layman-storage-path-change
  Title                     Layman storage path changed from version 1.3.0 on
  Author                    Sebastian Pipping <sping@gentoo.org>
  Posted                    2010-02-28
  Revision                  2

Layman has been using /usr/local/portage/layman to store
overlay checkouts from version 1.2.3 on.  As that path
was violating the concept of keeping portage away from
/usr/local the default of this storage location moves to

  /var/lib/layman

from version 1.3.0 on.  If you have never touched the file
/etc/layman/layman.cfg manually before, you may be tempted to let
tools like etc-update or dispatch-conf blindly accept this new version
of layman.cfg.

As that would hide all your currently installed overlays from layman
it's probably not what you want.  Your options are:

 A) Moving
   1. Move your current content to /var/lib/layman.
   2. Update PORTDIR_OVERLAY in /var/lib/layman/make.conf accordingly.
   3. Make /etc/make.conf source /var/lib/layman/make.conf.
   4. Set option "storage" in /etc/layman/layman.cfg
      to "/var/lib/layman".

 B) A symlink
   Put a symlink to your current storage location at /var/lib/layman
   before upgrading layman.

 C) Configuration
   Reject the path change for layman.cfg when running tools like
   etc-update or dispatch-conf.  Be aware with this way you'll have
   to do it for each layman update again.

PS: This news item is a reaction to users having run into this problem
(see bug #306233).  Thanks to Volker Hemmann for reporting.