Developer discussion for Creative Commons technology and tools

["SourceForge.net" <noreply AT sourceforge.net>]

Bugs item #1862853, was opened at 2008-01-02 18:37
Message generated for change (Settings changed) made by fourstones
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=559966&aid=1862853&group_id=80503

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: cchost
Group: cchost5_ccM3
>Status: Closed
>Resolution: Fixed
Priority: 3
Private: No
Submitted By: Victor Stone (fourstones)
Assigned to: Victor Stone (fourstones)
Summary: internal: cclib/ccextra need to be renamed

Initial Comment:
People who upgrade w/o svn will be hosed by all the file changes in 
cclib/ccextra - we'll need to rename/move these two dirs somewhere else 
before we go public.

----------------------------------------------------------------------

Comment By: Victor Stone (fourstones)
Date: 2008-01-02 21:49

Message:
Logged In: YES 
user_id=489789
Originator: YES

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..

----------------------------------------------------------------------

Comment By: Jon Phillips (kidproto)
Date: 2008-01-02 21:30

Message:
Logged In: YES 
user_id=914868
Originator: NO

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?


----------------------------------------------------------------------

Comment By: Asheesh Laroia (paulproteus)
Date: 2008-01-02 18:40

Message:
Logged In: YES 
user_id=142687
Originator: NO

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

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=559966&aid=1862853&group_id=80503