Will take chance for question here. <br><br>We ran into similar scenario as well when we designed virtualized Gentoo infrastructure and we found out that emerge/portage has not complete (read perfect) support for binaries (i.e. different USE flags for different machines).<br>
<br>Can you explain more about your project? It seems it really fits our needs. Some of our thoughts were to have this builder machine available as XEN domU, it would build the packages in chroot and then serve them to machines url&nbsp; as:<br>
<br>PORTAGE_BINHOST=&quot;<a href="http://packages.builder.domain/">http://packages.builder.domain/</a>&lt;machine-type&gt;/&quot;<br><br>Some other crazy ideas involved some extension to emerge/portage like: <br>Slave - hey, this is my /var/lib/portage/world, my USE flags (/etc/make.conf) and I want such and such package<br>
Master - calculating a bit and providing Slave with packages <br><br>(but this is overkill)<br><br>At the moment I have working prototype which is fine because machines are updated and it is doable, at the same moment it needs a lot of love because it is just a dirty hack (like scripts to easily start chroot, config apache, etc...).<br>
<br>I do not know catalyst much, all I know it is possible to do stage4 with this (i.e. build up2date XEN domu machine). I appreciate any hints on how to incorporate this into something slightly bigger.<br><br>I am looking for anyone interested in this, lets join effort guys.<br>
<br>Aloha,<br><br>Robert<br>