From: "Robert Šmol" <smol.robert@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] small distros - setups and practices?
Date: Mon, 5 May 2008 20:02:55 +0200 [thread overview]
Message-ID: <79342c4a0805051102lbeca0dek4d51fd5ac376ea67@mail.gmail.com> (raw)
In-Reply-To: <20080502154245.GA8698@bbone>
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
Will take chance for question here.
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).
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 as:
PORTAGE_BINHOST="http://packages.builder.domain/<machine-type>/"
Some other crazy ideas involved some extension to emerge/portage like:
Slave - hey, this is my /var/lib/portage/world, my USE flags
(/etc/make.conf) and I want such and such package
Master - calculating a bit and providing Slave with packages
(but this is overkill)
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...).
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.
I am looking for anyone interested in this, lets join effort guys.
Aloha,
Robert
[-- Attachment #2: Type: text/html, Size: 1500 bytes --]
next prev parent reply other threads:[~2008-05-05 18:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 12:18 [gentoo-catalyst] small distros - setups and practices? Max Arnold
2008-04-22 16:58 ` Chris Gianelloni
2008-04-23 2:03 ` Max Arnold
2008-05-01 17:04 ` Chris Gianelloni
2008-05-02 2:20 ` Max Arnold
2008-05-02 15:03 ` Chris Gianelloni
2008-05-02 15:42 ` Max Arnold
2008-05-05 18:02 ` Robert Šmol [this message]
2008-05-07 6:45 ` Chris Gianelloni
2008-05-05 19:41 ` Ramon van Alteren
2008-05-07 6:46 ` Chris Gianelloni
2008-05-09 10:02 ` Ramon van Alteren
2008-07-22 4:37 ` John Eckhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=79342c4a0805051102lbeca0dek4d51fd5ac376ea67@mail.gmail.com \
--to=smol.robert@gmail.com \
--cc=gentoo-catalyst@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox