How to use custom ebuilds
=========================

- create a new directory where you want to store your custom ebuilds
  (I'm using /usr/local/portage in this document)
- make sure that directory is readable by the portage group
- edit make.conf and set PORTDIR_OVERLAY=/usr/local/portage there
- for each package that you want to store in your overlay (using 
  app-misc/foo-1.0) as example here:
	- make a directory in PORTDIR_OVERLAY for the category/package name:
		mkdir -p /usr/local/portage/app-misc/foo
	- put the ebuild you have for that package in that directory
	- create a digest for that ebuild:
		ebuild /usr/local/portage/app-misc/foo/foo-1.0.ebuild digest
	- now you should be able to emerge that package just as any other package:
		emerge app-misc/foo

- if you want to use custom category names you have to list them in
  /etc/portage/categories (doesn't exist by default)
- if you want to use custom eclasses you can put them in PORTDIR_OVERLAY/eclass,
  however you should not override eclasses from the official tree or we won't be
  able to help you with ANY problem