[mythtv-users] Installing SVN to multiple machines

[Robin Gilks]

> Michael T. Dean wrote:
>> On 03/22/2008 03:36 PM, Robin Neatherway wrote:
>>>>  > Is there an easy process to make
>>>>  > a .deb or even just a tarball I could extract to /usr/local that
>>>> would
>>>>  > populate the necessary directories?
>>>>
>>>>  I do a "make install INSTALL_ROOT=/tmp/myth" then cd to /tmp/myth and
>>>>  make a tarball. Then on each of my FEs and BEs, I cd to / and untar.
>>>>  It's not pretty, but it works.
>>>>
>>>>  To uninstall, I manually delete files.
>>> Very good, I'll give this a go.
>>
>> But remember if you have non-compatible library versions (or even
>> slightly different architectures resulting in different instruction sets
>> being used), you may be installing non-working binaries onto your other
>> (non-build) system.
>>
>> Basically, if you're trying to go across distributions, not only are you
>> taking on the responsibilities of a packager (and look how busy Axel and
>> Mario* stay with that job ;), but you're trying to make packages that
>> work on multiple distros (with all their differences--layout,
>> configuration, installed libraries, library versions, ...).  I still say
>> identical is the best bet if you don't want to compile on each system.
>> If you don't have identical systems, you should really compile on each
>> distro (i.e. if you have 2 Ubuntu systems).
>>
> Just to emphasise here - if you have different *hardware* between boxes
> you are
> probably wasting your efforts attempting to save some compile time. Even
> two
> different video card *versions* may make libraries different, let alone
> any more
> significant differences between boxes.

I run a combined back/frontend on an Athlon XP and a separate frontend on
a Via Epia and the way I get round it is run a chroot of the Via box on
the main Athlon machine, build all its' software within it (both boxes are
Gentoo) and diskless mount the Via onto the server.

I compile MythTV for i686 generic and mount --bind the source into the
chroot the Via box uses and just do a 'make install' from the one common
source tree. This links everything to the correct libs and I said above,
I've made a point of making the instruction set optimisation the lowest
common denominator!

At least I know I have common versions of the libs etc, even if they have
been individually compiled with full optimisation for each architecture,
so I know their APIs are the same.

Anyway, it works for me :-)  and has for the last 2+ years...

-- 
Robin Gilks