Hi Giovanni,
> Your approach of multiple smaller repositories is appealing
> for all the
> reasons you mentioned, as well as speeding commit scans, but there is
> one significant problem - "commit" and "update" are
> asymmetric - they do
> slightly different things when used with folders containing externals.
So you set up OBR and use externals to link inside that repository?
> 2. Software I'm writing : several hundred MB, pretty much
> all in Delphi
Another Delphi addict. Welcome to the show!
> From this I create a "Workspace" of about seven folders all
> extracted as
> EXTERNALS,
> - all of the "Software" repository (so I can move bits about easily)
> - bibliography <-- pulled from MyResearch
> - admin <-- pulled from MyResearch
> - and several others <-- pulled from MyResearch
I set up this kind of workspace structure "per project" since there are some
libraries we use in many projects. These are linked via svn:externals
I also version my Delphi packages, but these are in a predefined location
(companywide), because Delphi wants the compiled output of the packages to
be in the windows search path.
> Significant Problem - Worse with More Repositories:
>
> 1. "Commit" on the workspace **FINDS** all the files that should be
> committed in the "externally" linked subdirectories,
> but doesn't
> actually commit them.
>
> ==> there's NO SINGLE COMMAND to "Commit all External
> Subfolders"
> which means it easy to forget some.
I'm actually happy with this assymetry. It makes me think twice before
committing svn:externals, because I know that they are used in other
projects as well, so it might be easy to break a lot of things.
> them all with the same user-defined commit message. This
> isn't hard but
> it seems like something Tortoise (and Subversion) should do, otherwise
> there's a noticeable asymmetry between "update" and "commit"
> on folders
> containing "svn:external"
>
> --> Am I missing something?
> If not, could I suggest a "Commit all Externals" menu
> item in TSVN.
Sounds doable, but that's Stefans decision. I'd suggest to change the
behaviour when TSVN finds changes in externals down the path. The warning
"Found changes in externals, not committed" could be changed to "Found
changes in externals. Should they be added to a separate commit? (Y/N)".
Then TSVN could pop up a commit dialog for each set of changed externals.
This would require a mulit stage commit. I would not try to commit
everything in one go, even if the externals point to the same repository
(Don't know if it would be possible at all, but it sounds too complicated)
> Thanks for your efforts all. Apart from a few aborted "commits" caused
> by "Folder already exists", TSVN and Subversion have run
> flawlessly for
> months - I'm going to point my students at it this year.
>
> --> Could I suggest a option during "Update":
>
> "Folder "foldername" already exists - Delete & Continue Update?"
>
> rather than just aborting - it took me ages to find some of these.
Sounds reasonable, would be the same option for files. "Overwrite & Continue
Update". Again I don't know if this is possible. The update is run via the
subversion library and I don't know if this process can be made interactive
at all. If not, you should request this on the svn developer list.
Cheers
- Lübbe
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Feb 21 10:24:35 2005