Working with hierarchical repositories
Lester Caine
lester at lsces.co.uk
Wed Sep 14 08:02:34 UTC 2011
Marco Gerber wrote:
> It's hardly impossible to share eclipse project / workspace files over multiple
> machines. We tried this out ;-). It seems to me that the only one solution is to
> make a copy (script based) and let mercurial manage changes of this copy.
> However, I'm looking for a way without scripting (to avoid two worlds, mercurial
> and a script).
Actually, there is no reason you could not clone the .project file - I've just
checked and there is nothing in there of importance. It's the .metadata folder
in the workspace that has all the OS specific bits - and that includes the lock
file for each eclipse instance. But the workspace can hold many projects - all
of which are checked out from hg in my case, so cloning a complete set of
projects + eclipse configuration is a layer above simply checking out a project?
And I HAVE to use scripts at that upper level to manage the more complex
projects since submodule is not totally functional where the end target is
pigging github ;)
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
More information about the Mercurial
mailing list