By juanzo007 on

Hi folks,

I'm having a bit of trouble with svn. I'd like to create my own drupal repository that holds all the particular themes, contrib modules I will use. Simple enough...

I get confused with how to update that repo as changes to drupal core get released. the way i've gone about it so far is to download a svn working copy from acquia drupal, then import that working copy into my repository. what i cant get my head around is how to then update my repository as the acquia drupal core changes.

I have the feeling this is a very simple process, but there is something fundamental I'm missing. Any advice?

Many thanks!

John

⋅ Categories: Drupal 6.x

Comments

juanzo007’s picture

juanzo007 commented

disregard... i was under the impression that if I was building a site, that version control was necessary. apparently not, but i guess it comes into play when you are rather deeply customizing stuff. wish i knew that 3 days ago! onward...

Anonymous’s picture

Anonymous (not verified) commented

Personally, I don't think your efforts to setup a svn was a bad idea. In fact more of that should be encouraged so that you can see what changes you have made and you will always have a record of any changes made.

If you are working on your own custom theme... very handy. I am sure all of us have had moments when we were like... I wish I hadn't done that.

rocheking’s picture

rocheking commented

I have an acquia drupal install. I set up my server to connect my web root folder to the acquia drupal svn server.

If I add themes etc to the sites/all/themes folder and modules to the modules folder, or make other changes, will I lose them when I svn up ?

Do I need to version control my local copies? If so, I'll connect them to the same svn url. But I don't see how that will help, since my local copies and those on the server are independently connected to the svn.

My hope is that this is a non-issue and that I can add and alter at will, but somehow I suspect my updates will get hung up and fail or revert my changes. My hosting company had .htaccess in my webroot by default and that caused my svn co and up commands to halt because there was (I guess) an unversioned file of the same name. So maybe as long as I don't have any name conflicts I'm ok. And in the cases where there is an issue maybe I can use diff or other svn commands to work it out case by case (there shouldn't be a lot of updates to the acquia versioned code (maybe .htaccess or settings etc so no big deal ?)) ???