[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Re: Keeping the Original File at the same State as the Repository

From: Jus Age <jusage_at_live.de>
Date: Fri, 22 May 2015 02:11:55 -0700 (PDT)

> On 21 May 2015 at 09:57, Jus Age <jusage at live dot de> wrote:
>
> > > On Tue, May 19, 2015 at 10:22 AM, Jus Age <jusage at live dot de> wrote:
> > > >
> > > > Hey everyone,
> > > >
> > > > I'm sure this is kind of a stupid question. I couldn't find anything
> > > helpfull except for Local Versioning Systems, which all seem either
> > Command
> > > Line based or already outdated.
> > > > My question now is, is there a way to get the original Files that I
> > > Imported into the Repository also at the same state as the Repository
> > > Version?
> > > >
> > > > The problem is, we want to Version some of Config Files of a tool that
> > > runs on a Server.
> > > > There are several different People accessing this Server with their own
> > > accounts. So the Working Space for the Repository will be held in their
> > own
> > > Home Directories.
> > > >
> > > > But the problem is that the Software that needs these Config files can
> > > only work with them if they are in their Directories, I can't set it up
> > so
> > > that it takes them with a file:///, https:// or svn: Link.
> > > >
> > > > I was hoping that the actual File would also be updated when I do a
> > > commit, but it seems that Subversion is designed to only keep the
> > > Repository in the newest state (which makes sense on the way it is ment
> > to
> > > be used).
> > > >
> > > >
> > > > So is there any way for me to get what I want from TortoiseSVN?
> > > >
> > > >
> > >
> > > I guess, if you're going to do this with SVN, that you want a tool that
> > > monitors the repository for changes, and when it sees a change, allows
> > you
> > > to specify an action to take (for example, running `svn update` on a
> > > working copy to pull in the changes, or downloading individual files with
> > > `svn cat`).
> > >
> > > Commit Monitor is one such tool, designed to work with TortoiseSVN. If
> > you
> > > wait until version 1.9 comes out, I understand a similar tool is
> > integrated
> > > into TortoiseSVN.
> >
> >
> > Not sure if I understand this correctly. For me this sounds more like an
> > automated way of Updating the Working Copies.
> > But my problem is that the initial File that I imported into the
> > Repository is not changed automatically if something is Committed to the
> > Repository.
> > Or that I don't know how to do this. Is there maybe a way to create a
> > repository with an existing File so that this will be updated once someone
> > commits something?
> >
>
> Subversion doesn't push changes out to the clients. That is not what it was
> intended for. Sounds like you want something more like a file sharing
> utility.
>
> But if you want to use Subversion, what Ben is suggesting is that you make
> the users' home directories a working copy and update them all from the
> same repository. But the update has to be done on they client side.
>
> You can set up a repository hook which sends an email to notify people that
> they need to update.
>
> Simon

Hey Simon,

thanks for your response. I'm not sure if it is me that does not say it correctly. In any case I think we are talking about different things.

I don't want to get anything pushed to the Users and their Working Spaces.

Let me try to explain it like this:

Original File:

C:/SVNTest/Test.txt (Empty File)

Repository:

C:/SVNRepository

Import C:/SVNTest/Test.txt into C:/SVNRepository

mkdir C:/Users/MyName/SVNTest

SVN Checkout C:/SVNRepository in C:/Users/MyName/SVNTest

Update C:/Users/MyName/SVNTest

va C:/Users/MyName/SVNTest/Test.txt

(change something in it and save it)

Commit C:/Users/MyName/SVNTest

Now the Test.txt in the Repository (viewable through the Repo-Browser) has the changed Values in it.

But the File C:/SVNTest/Test.txt is still empty, it is not updated.

This is the problem I want the C:/SVNTest/Test.txt to be updated as well if someone commits something.

In this example it is a local installation since we are testing right now. In the end it shall be a Server installation with a Shared Drive Repository and Workin Spaces in the Home Directorys.

Hope this explains it a little bit better what I want to archive.
I got a clue on this already, that the Hook's could maybe help me with this?

Thanks for your help so far.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3118706

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-05-22 11:12:03 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.