Issue:  Doing an 'emerge sync' to sync our portage tree will remove older
	ebuilds.  As a result, this prevents us from then being able to
	install older packages via an 'emerge' call because the corresponding
	ebuild(s) no longer exist in the portage tree.  If a user is still
	interested in running tests against these older packages, we need to
	find a way for them to still have access to that ebuild so they may
	continue to test.  Here are some of the possible solutions:

Solution 1:
-----------
There is no anonymous CVS access for gentoo's portage tree (well, there is
no anonymous access yet. . . I read some email that they are working on it)
However, you can use ViewCVS to grab older ebuilds via this link:

http://www.gentoo.org/cgi-bin/viewcvs.cgi/

There is a guy who has set up his own anon-cvs server:

http://article.gmane.org/gmane.linux.gentoo.portage.devel/656

However he states he refuses to host the gentoo-x86 branch which is the
one we are interested in (gentoo-x86 is where the ebuilds reside)

If and when there is ever anonymous access to CVS, both users and ourselves
can just pull from cvs.  Until then, a user can download and install the
individual ebuild via the ViewCVS link.  (we can easily walk them through
where to place the ebuild, how to digest it, and emerge it or write a script
to do this for them)

Solution 2:
-----------
Second solution is to set up our own gentoo mirror and don't delete the older
existing files.

This link tells how to set up an rsync mirror:
http://www.gentoo.org/doc/en/rsync.xml

What we'd actually want to do is set up a private rsync mirror just for our
internal use.  This will prevent any bandwidth issue if we were to publicly
host the mirror.  The issue we face having the mirror be internal is that
we are then responsible for creating and exporting portage tarballs that
users will need.  The other issue is space availability on the machine we
will be hosting.  The docs say to allow 250MB of space for a portage tree.
That however is the portage tree with the older ebuilds removed.  Since, we are
not deleting the oder ebuilds, we need to account for much more space and
expect it to continually grow.

Recommendation
--------------
Right now I would learn towards using the ViewCVS solution to download older
ebuilds.  It's maintained externally, easily accessible, and requires minimal
extra work on our end.  All we need to do is document some manual steps to
download the ebuild in question, move it to the PORTDIR_OVERLAY directory,
digest it, and install.  We should also script this up.