Thanks for chipping in on this, I really appreciate it.
On Wed, 2009-12-02 at 00:21 +0000, Martin Pool wrote:
> 2009/12/2 Russel Winder <email address hidden>:
> > Can't do that cleanly as far as I know (and Martin tells me) as I have
> > my bzr.dev shared by Ubuntu 32-bit and 64-bit, Mac OS X and Solaris.
> > NFS mounts -- but you probably knew this given my loud irritation at
> > Linux and mmap and TDB and bzr-svn/bzr-git (not anything that
> > bzr-svn/bzr-git can do about it though :-(
>
> If you run 'setup.py install --home ~' then I think it will install
> the extensions into per-architecture directories under ~/lib, so they
> will stay up to date. You will need to re-run this after each update
> of bzr.dev. If it doesn't work, please either ask or file a bug as
> appropriate.
OK, that would solve the "technical" issue of having the checkout of
bzr.dev shared by many different architectures and yet still compiled.
However, the problem that remains is a "management" one, in that every
time I updated I would then have to login to each machine and run the
compilation (though I guess I could script such a compilation for all
the permanently connected machines). The huge advantage of not
compiling is that it works on all architectures just by updating on the
server and (I think this is the real "killer" point) I can Unison
synchronize the server copy to the laptops and back again in the full
knowledge that Bazaar will Just Work (tm) on all my machines.
NB I appreciate I get a performance hit by not compiling but the ease of
management across 7 machines outweighs this.
PS Matt's suggestion coming up prompted me to "do the right thing" and
I am now up to date with revision 4850.
Martin,
Thanks for chipping in on this, I really appreciate it.
On Wed, 2009-12-02 at 00:21 +0000, Martin Pool wrote:
> 2009/12/2 Russel Winder <email address hidden>:
> > Can't do that cleanly as far as I know (and Martin tells me) as I have
> > my bzr.dev shared by Ubuntu 32-bit and 64-bit, Mac OS X and Solaris.
> > NFS mounts -- but you probably knew this given my loud irritation at
> > Linux and mmap and TDB and bzr-svn/bzr-git (not anything that
> > bzr-svn/bzr-git can do about it though :-(
>
> If you run 'setup.py install --home ~' then I think it will install
> the extensions into per-architecture directories under ~/lib, so they
> will stay up to date. You will need to re-run this after each update
> of bzr.dev. If it doesn't work, please either ask or file a bug as
> appropriate.
OK, that would solve the "technical" issue of having the checkout of
bzr.dev shared by many different architectures and yet still compiled.
However, the problem that remains is a "management" one, in that every
time I updated I would then have to login to each machine and run the
compilation (though I guess I could script such a compilation for all
the permanently connected machines). The huge advantage of not
compiling is that it works on all architectures just by updating on the
server and (I think this is the real "killer" point) I can Unison
synchronize the server copy to the laptops and back again in the full
knowledge that Bazaar will Just Work (tm) on all my machines.
NB I appreciate I get a performance hit by not compiling but the ease of
management across 7 machines outweighs this.
PS Matt's suggestion coming up prompted me to "do the right thing" and
I am now up to date with revision 4850.
Thanks.
-- ======= ======= ======= ======= ======= ======= ======= ======= ======= =======
xmpp: <email address hidden>
Russel.
=======
Dr Russel Winder Partner
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:<email address hidden>
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder