Note: The old live ebuilds are available at our project page.
Installation
Refer to the official Howto The Portage Manual for thorough explanations of portage and the emerge process.
1.PORTDIR_OVERLAY is a feature in portage making it possible to add your own ebuilds. These will not change the portage-tree and will not be overwritten by an rsync. To use this feature, simply remove the hashmark in /etc/make.conf
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
# concern that they will be deleted by rsync updates. Default is not
# defined.
PORTDIR_OVERLAY=/usr/local/portage
# concern that they will be deleted by rsync updates. Default is not
# defined.
PORTDIR_OVERLAY=/usr/local/portage
2.Now we must make a few directories. In addition to the PORTDIR_OVERLAY itself, one dir for the category, and one for the actual ebuild that you want to use. It is important that one uses the official categories from portage. In this example we will use category kde-misc, ebuild krusader-cvs-1-r4.ebuild and architecture x86
$ mkdir /usr/local/portage
$ mkdir /usr/local/portage/kde-misc
$ mkdir /usr/local/portage/kde-misc/krusader-cvs
$ mkdir /usr/local/portage/kde-misc
$ mkdir /usr/local/portage/kde-misc/krusader-cvs
3.The next step is to copy the ebuild into the ebuild directory and generate a digest
$ cp /path/to/krusader-cvs-1.ebuild /usr/local/portage/kde-misc/krusader-cvs/krusader-cvs-1-r4.ebuild
$ ebuild /usr/local/portage/kde-misc/krusader-cvs/krusader-cvs-1-r4.ebuild digest
$ ebuild /usr/local/portage/kde-misc/krusader-cvs/krusader-cvs-1-r4.ebuild digest
Note: For live ebuilds we will only get a Manifest.
4.Introduce our new ebuild to portage
$ echo "kde-misc/krusader-cvs ~x86" >> /etc/portage/package.keywords
Note: As of portage-2.0.50. You might have to create /etc/portage/ first.
5.Finally we install the ebuild
$ emerge krusader-cvs
Note: Repeat this step each time you want to update Krusader from CVS.










