Hello Farzad,
here's a bit more thought.
On Monday 27 October 2008 Farzad FARID wrote:
> 1) Selecting the right repository the first time
Maybe there'll be a "fsvs switch -u <destination url> <entry>" command, to do
the unversioning/commit in one command.
> 2) Putting /etc/fsvs in the right repository
>
> I'm versionning "/etc", so "/etc/fsvs" MUST be handled by the "local"
> URL/repository, of course :)
>
> That's because each server sharing the common "base" URL/repository must
> have it's own configuration. I don't think this is mentionned in the
> Master/Local HOWTO?
As soon as the URLs are no longer in /etc, it might make sense to put the rest
in the common URL.
> 3) Handling mixed-repository commits
Yes, I'll try to get multi-URL commit working.
> An error occurred: Name does not refer to a filesystem directory (160016)
> in ci__work: editor->close_edit: Path 'fsvs' not present
>
> As Phil explained, it is normal to have an error here, but practically it
> is very tedious to handle.
No, it ain't; I'll take a look.
> 4) Adding a second server to the common "base"
...
> From them on, I had a hard time getting the 2 servers in sync! This is
> because I did not install the 2nd server from scratch: I had to resolve
> the differences between the 2 servers by hand.
>
> This situation is not FSVS's fault. But I know I had to use "fsvs
> sync-repos", "fsvs update", "fsvs commit", "fsvs add", "fsvs unversion",
> "fsvs revert" multiple times, in multiple orders, on *both* servers..
...
> I'm still manually resolving minor conflicts on the 2nd server with "fsvs
> revert". I takes some time, but it works fine. Using "fsvs status -vC |
> fgrep - v '......'" was the best solution I could find
You might try "fsvs status -vC -fnone,meta,text" - that should omit the
non-changed entries.
I think I should add a shortcut for that.
> to list all the
> changes and determine if they are minor (just a date diffence in most
> cases) and can be reverted on the 2nd server in order to be in sync with
> the 1st one.
Hmmm ... do you have any suggestions how to make that easier?
> So far nothing broke :) I haven't lost a single file, and installing FSVS
> even helped me spot oddities, like files which should have been identical
> on the 2 servers, but were not.
That's good.
> 5) Choosing the SVN directory structure
>
> My customer and I chose the following tree:
Thank you for this illustration!
> My Suggestions:
> --------------
>
> - In mixed-repository cases, one solution would be that FSVS checks which
> files belong to the repository I am committing to, and *ignores* files who
> don't belong to it.
It should do that - only entries from this repository (and new ones, that have
no association yet) are taken.
> - Another solution would be to have an option to explicitely *exclude*
> files or directories from a commit command.
Do you know about the filter option?
And I already thought about allowing something like patterns on the commit
(and status) commandline - to avoid having to specify individual entries.
> - My prefered solution is that FSVS uses the information it already has to
> determine where to commit each file.
It should.
> The "priority" parameter of each URL
> could resolv conflicts.
It should do that, too - although I think we're speaking about different kinds
of conflict.
> - What about adding an option to "fsvs status", to display the URL alias of
> each file/directory?
Good idea.
> - Finally, in a multiple URL configuration, I find myself using the "-o
> commit_to=XXXX" very often! It'd be nice to have a shortnamed command line
> option for this :)
As soon as you've got the entries at the correct locations, I'd thought that
switching the URLs wouldn't be so often needed.
But I think you've got more experience with multi-URL operation than I do ;-)
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
