U++ forum: Welcome to the forum

Re: SVN plan... [message #12641 is a reply to message #12640]

Mon, 12 November 2007 00:49

mdelfede
Messages: 1307
Registered: September 2007

Ultimate Contributor

mr_ped wrote on Mon, 12 November 2007 00:25

".svn directories in the source tree"

I'm not sure what's so wrong with these, never really got into my way.

on Linux they don't appear (hidden files), on windows they may disturb a bit... but I agree, not a real problem

Quote:

"automatic detection of delete/rename -> so that in the end, we have "single click" solution available (makes smart check/commit)."

a) personal preference, I personally prefer to do this manually as I often have some files in directory which are only local and shouldn't be added to repository.
In the end I can't even imagine "one click update" working for me, as sometimes I start to work on two changes in the same time, and commit them afterwards by hand as two distinctive commits, if those changes are completely independent and in different files.

b) TheIDE can on package management level do this, so the files within .upp will be automatically deleted/added into svn with next commit.

I agree, that should be separate from svn plugin. TheIDE *can* send an additional command to svn to tell him to add or delete files, it's quite easy, but that should be done only for ide managed files. It should not touch files outside packages.

Quote:

"some sort of local repository to browse at least some revisions (not necessarily all in SVN repository)."

offline usage? I don't know how to solve this one effectively (svn has no direct support for local repositories), there's some way export/import repository so doing a local ("read only") copy is possible, but it would be a standalone copy not connected with main repos and I have no idea about means of syncing to main repos (without another full export/import).

The svn is based around central server, so something like committing to local repos is not possible at all. (unless you take all the commits from local repos and redo them on the central server again = lot of hassle)

Well, that's the usual point on local/remote repositories.
I do prefere a central repo too, maybe with a local read-only one kept in sync for regression tests (it's much faster).
Inside theide it would be nice to have the (optional) ability to create and mantain an additional local svn repo, in sync with the remote one. It would also be interesting the possibility to 'go back' to an older revision locking the repository in order to avoid unwanted updates during regression tests and, maybe, the ability to check out an arbitrary revision on a different local path, for tests purposes.

Max

Report message to a moderator