Discussions  >  CollabNet Subversion Client  >  Re: How to version-control non-code files related to projects

Hide all messages in topic

All messages in topic

RE: Re: How to version-control non-code files related to projects RE: Re: How to version-control non-code files related to projects

Author mwunderlich
Full name Martin Wunderlich
Date 2012-02-06 07:04:54 PST
Message OK, I have just tried with a test file. It looks versioned alright, but the handy icons provided by TortoiseSVN aren't there. Would you know why that might be?

Cheers,

Martin

Re: How to version-control non-code files related to projects Re: How to version-control non-code files related to projects

Author markphip
Full name Mark Phippard
Date 2012-02-06 05:16:57 PST
Message On Feb 6, 2012, at 5:00 AM, Martin Wunderlich wrote:

> I have tried your suggestion of adding a specific folder now and added some files and folders to it using Tortoise. So far so good. However, it seems that no connection is created to marked the added files as versioned by SVN. At least, I don't see the hidden .svn folder an there aren't any icons displayed in explorer view.
> Do I need to explicitly checkout these files into their current location after uploading them to the repository?

Yes, you need a checkout from the repository in order to have a working copy from which you can do subsequent commits or updates.

Mark

Re: How to version-control non-code files related to projects Re: How to version-control non-code files related to projects

Author markphip
Full name Mark Phippard
Date 2012-02-06 05:16:20 PST
Message On Feb 6, 2012, at 2:21 AM, Martin Wunderlich wrote:

> thanks a lot for the reply. By "top-level folder" do you mean a new repository or a new folder at the root of this project's repository?

By top-level folder I mainly meant a folder outside the tree of your current project, since you seem to want to check it out separately to a different server. Since you cannot check out a single file, you have to put the files in unique folders that can be checked out without pulling in files you do not want.

Mark

RE: Re: How to version-control non-code files related to projects RE: Re: How to version-control non-code files related to projects

Author mwunderlich
Full name Martin Wunderlich
Date 2012-02-06 05:00:38 PST
Message Hi Mark,

I have tried your suggestion of adding a specific folder now and added some files and folders to it using Tortoise. So far so good. However, it seems that no connection is created to marked the added files as versioned by SVN. At least, I don't see the hidden .svn folder an there aren't any icons displayed in explorer view.
Do I need to explicitly checkout these files into their current location after uploading them to the repository?

Cheers,
 
Martin

RE: Re: How to version-control non-code files related to projects RE: Re: How to version-control non-code files related to projects

Author mwunderlich
Full name Martin Wunderlich
Date 2012-02-06 02:21:58 PST
Message Hi Mark,

thanks a lot for the reply. By "top-level folder" do you mean a new repository or a new folder at the root of this project's repository?

Kind regards,

Martin

Re: How to version-control non-code files related to projects Re: How to version-control non-code files related to projects

Author markphip
Full name Mark Phippard
Date 2012-02-02 08:54:08 PST
Message Subversion only versions trees, not individual files. So you might want to add one or more top-level folders for these different files so that they can each be versioned independently. You could just configure the svn:ignore property on the folders so that files in the same folder that you do not want versioned are ignored.

Alternatively, you might add a folder in your app for all these files so that they can be edited and versioned with the app itself. You would then need a separate process to use svn export or svn cat command to extract the file from the repository when it changes.




On Feb 2, 2012, at 8:23 AM, Martin Wunderlich wrote:

> Hi all,
>
> I have a somewhat generic question on SVN version control: How do you go about versioning and storing files that are not source code, but rather related files? I am thinking about things such as:
> - installer files
> - build scripts
> - configuration files
> etc.
>
> FWIW, we are using the AnkhSVN client in VS2010. The product is written in VB.net. In our case, the files mentioned above are situated in various locations on file servers, together with other stuff. So, there is not a single directory location that could serve as source for the repository upload. I would like to maintain the location structure of these files (because other stuff depends on these locations) and add them to the product's repository at the same time (so that we can go back to older versions when needed).
>
> What's the best way to achieve this?
>
> Cheers,
>
> Martin
>
> --------------------​--------------------​--------------
> http://subversion.op​en.collab.net/ds/vie​wMessage.do?dsForumI​d=4&dsMessageId=​444927
>
> To cancel your subscription to this CollabNet Subversion Client discussion, please e-mail forum4-unsubscribe@s​ubversion.open.colla​b.net.

How to version-control non-code files related to projects How to version-control non-code files related to projects

Author mwunderlich
Full name Martin Wunderlich
Date 2012-02-02 08:23:07 PST
Message Hi all,

I have a somewhat generic question on SVN version control: How do you go about versioning and storing files that are not source code, but rather related files? I am thinking about things such as:
- installer files
- build scripts
- configuration files
etc.

FWIW, we are using the AnkhSVN client in VS2010. The product is written in VB.net. In our case, the files mentioned above are situated in various locations on file servers, together with other stuff. So, there is not a single directory location that could serve as source for the repository upload. I would like to maintain the location structure of these files (because other stuff depends on these locations) and add them to the product's repository at the same time (so that we can go back to older versions when needed).

What's the best way to achieve this?

Cheers,

Martin
Messages per page: