About the original topic: He would just have to keep a eye on how he adds the packages as at some stage it gets too far from the SL branch and can cause havoc trying to find errors / fixes etc and still mixing and matching or try to recover using both and different tree's, git merge might be the only solution and lots of skill.
Either go all the way from SL to source portage and maintain that direction / tree / branch or stay as close to SL tree as possible with a few extra programs / packages if using the livedvd full install.
Server / Core install, source packages should be fine as you would likely not use much of the equo packages only to get started and then change direction.
Somewhere you would loose either emerge or equo as one will take precedence and the tree you are using.
Very sensitive areas is python and dependent programs + equo + sqlite and having something go wrong here leads to lost of fun eventually breaking emerge and a few others leading to a snowball effect trying to catch this. Best is to keep making bin packages just in case you need to start over and have a copy of /var/lib/entropy as well as /usr/portage for faster recovery times especially with using git.
Try to see if using say funtoo get the portage-2009-????.bz2 snapshots and below mention package folder as alternative.
Have a look at this:http://en.gentoo-wiki.zugaina.org/index.php/HOWTO_setup_a_PORTAGE_BINHOST_serverConfigure your make.conf (server side) - Code: Select all
cd /var/db/pkg/; for i in */*; do quickpkg --include-config=y =$i; done
As well as alternative daily backup to say external hd "/mnt/hd2/packages" of say your PKGDIR="/backup/packages" in make.conf and using this above to build to it. Use caution with "eclean packages" as some old and new ones will be needed during redo after clean install or once you are about where you need to be = format and rebuild using bin's you created.
LOL I had to do this a few times

after the crazy Mexican fireworks outside. Damn they are loud. LOL
Hope this makes sense and helps.