Current Subversion ebuilds assume that if berkdb is not in the USE flags, we should get a client-only build. So, without berkdb, Apache config examples, Python bindings, etc. are not installed. This is a broken assertion. Since version 1.1-rc*, Subversion can use its own filesystem (fsfs) that works way better than BerkeleyDB. It's perfectly legitimate to build a svn server without BerkeleyDB.
I'll install the apache config files. I'll also check whether the bindings do actually compile correctly without db (they didn't). Btw. the assumption that without berkdb would be a client-only build is more a subversion assertion than an ebuild assertion.
Just fixed in CVS