Re: [gentoo-user] building a binary distribution

[Sathish Vasudevaiah]

>You can make a chroot with a generic install for building binary
>packages[2] and use it as a binhost[1]. Or you can use crossdev to
>create an environment and use distcc[3] so your fast machine will
>compile packages for you. I've used both and distcc seems a bit more
>clean and transparent, while a little harder to configure (I had to
>mask some crossdev packages till I get a usable configuration, but
>after that, it works flawless).

Thanks, I went through the references..
The distcc-crossdev approach seems to assume that
all of the upgrade actions start from the slow machine
but get executed on the fast system. And there is no
saving of the intermediate results (binary packages)

On the mythtv machine there is a spare partition 
created for testing. I am thinking of the following
approach 
- create all the binary packages
- NFS mount the spare partition
- install the binary packages and boot up with
  the spare partition for testing.

This should leave the mythtv system with a working
setup all the time. In this case, how do I bootstrap
the spare partition ? Should I start with the gentoo
livecd or do a 'dd' from the working partition to the
spare one ?

>I didn't need ultra-fancy CFLAGs optimization, so I'm now using the
>Gentoo system that is the main OS on that "big iron" for providing
>binary packages, trading off a few CPU cycles for not doing all
>possible optimization.
>You have many options, but it certainly depends on what machines you
>have for doing the compilation work. If their architecture doesn't
>match that of the targeted machine, you can do cross-compiling, but

In my case it is the stability..the safe cflags gentoo doc
is indicating that "march=c3..." so this probably means cross
compilation.



thanks
sathish





-- 
gentoo-user@g.o mailing list