Aeacus

Aeacus is a Gentoo overlay, that is meant to care of its users and ebuilds.

• Getting started
• Information for users
• Repository
• Issue tracker
• Listfile for Layman

Getting started

# emerge -nav layman mercurial
# layman -o http://hades.redsecure.ru/aeacus/layman-list.xml -a aeacus

If you never worked with Portage overlays before, please read Gentoo Overlay Guide

You need to emerge dev-util/mercurial and app-portage/layman for this to work. There is a less automated approach, that does not require these tools, but I guess you can figure it out yourself.

To start using Aeacus, add its listfile to 'overlays' variable in /etc/layman/layman.cfg. It should look like this:

overlays  : http://www.gentoo.org/proj/en/overlays/layman-global.txt
            http://hades.redsecure.ru/aeacus/layman-list.xml

Then just fetch the list with "layman -f" and add Aeacus with "layman -a aeacus".

You may also want to unmask any packages, that appear in Aeacus and have been masked in official tree. You can link profiles/package.unmask file to your /etc/portage/package.unmask directory.

Information for users

You are encouraged to use issue tracker to file any requests you may have, for example:

New packages, not present in Gentoo yet

• Use this template to start a new bug;
• Edit the bug to fit your package (notice the URL and summary fields);
• Add anything you might want to add (for example, links to forums/mailing-lists that contain wild ebuilds of this package);
• Submit the bug and wait for its resolution;
• While you wait, you may try your strengths and see what you can do yourself at developers' section below.

New versions of existing packages

• Use this template to start a new bug;
• Edit the bug to fit your package (note the version in summary field);
• Changelog and highlights are optional, but it might be interesting for developers/users that would improve their reaction time. You may also use release announcement page as URL for this bug.

Bugs in existing software (including compilation errors)

• Use this template to start a new bug;
• Edit the bug to fit your issue; please follow bug writing guidelines and supply as much info as possible;
• Submit backtrace, emerge --info, or compilation output as attachment;
• Remember to keep developers posted in case they need additional information.

Information for developers

Aeacus uses Mercurial to track all changes. To checkout current repository snapshot use the following command:

$ hg clone http://hades.redsecure.ru/aeacus/hg/ aeacus

This will create directory 'aeacus' with the current snapshot. You may edit it as you wish, but remember to use hg command to do any file hierarchy modifications (adding files, creating directories, moving, renaming, etc.). To get the patch, that you can attach to a bugzilla bug, or send me, first update your copy to the newest version:

$ hg pull -u

And then create a patch:

$ hg diff > my-patch.patch

More information on distributed SCM and its cool features can be found at Mercurial homepage.