Creative Commons Tools

caveat: I'm probably missing something:

People WITH svn are fine, they'll just do 'update'

People WITHOUT svn would be hosed if we don't rename those directories
because they will have deprecated modules lying around intermingled with
new code. In the case of ccextras this is disaster because they would be
picked up automagically on every page hit.

ftr the following system dirs/files are already obsolete:
cctemplates
ccfiles
cctools
cc-config-db.php


I'll admit I'm a little at a loss as to what this has to do with visible
.svn dirs or mixter specific directories..

Well, do you all think that having .svn directories visible in
non-unix-based OS is ok? Most ppl. who use ccHost are running apache,
right, so it shouldn't make a difference, right?

Let me know and I'll update...however, I would say, that there are some
directories removed from the shipped install, which are in SVN...so one
would need to do an svn up and then svn switch to update...

I'm all for this and also moving ccmixter specific code to another repo.
Thoughts on the both of the above?

Maybe in the future, checkouts can include the .svn directories so that
"svn switch" can be the recommended upgrade path?