| 1 |
Will take chance for question here. |
| 2 |
|
| 3 |
We ran into similar scenario as well when we designed virtualized Gentoo |
| 4 |
infrastructure and we found out that emerge/portage has not complete (read |
| 5 |
perfect) support for binaries (i.e. different USE flags for different |
| 6 |
machines). |
| 7 |
|
| 8 |
Can you explain more about your project? It seems it really fits our needs. |
| 9 |
Some of our thoughts were to have this builder machine available as XEN |
| 10 |
domU, it would build the packages in chroot and then serve them to machines |
| 11 |
url as: |
| 12 |
|
| 13 |
PORTAGE_BINHOST="http://packages.builder.domain/<machine-type>/" |
| 14 |
|
| 15 |
Some other crazy ideas involved some extension to emerge/portage like: |
| 16 |
Slave - hey, this is my /var/lib/portage/world, my USE flags |
| 17 |
(/etc/make.conf) and I want such and such package |
| 18 |
Master - calculating a bit and providing Slave with packages |
| 19 |
|
| 20 |
(but this is overkill) |
| 21 |
|
| 22 |
At the moment I have working prototype which is fine because machines are |
| 23 |
updated and it is doable, at the same moment it needs a lot of love because |
| 24 |
it is just a dirty hack (like scripts to easily start chroot, config apache, |
| 25 |
etc...). |
| 26 |
|
| 27 |
I do not know catalyst much, all I know it is possible to do stage4 with |
| 28 |
this (i.e. build up2date XEN domu machine). I appreciate any hints on how to |
| 29 |
incorporate this into something slightly bigger. |
| 30 |
|
| 31 |
I am looking for anyone interested in this, lets join effort guys. |
| 32 |
|
| 33 |
Aloha, |
| 34 |
|
| 35 |
Robert |
Archives