From: Marius Mauch <genone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC - Gentoo on the Lab
Date: Mon, 22 Aug 2005 16:38:11 +0200 [thread overview]
Message-ID: <20050822163811.3dcc8fde@andy.genone.homeip.net> (raw)
In-Reply-To: <20050822025840.6bb9bdb9@acme.rjlouro.org>
On 08/22/05 Ricardo Loureiro wrote:
> 1- Can I RSYNC_EXCLUDE everything except profiles and have an usable
> system?
Define "usable". As only portage uses the tree it would be the only
thing that might break.
> 2- There was a portagesql effort, is it dead?
As far as I know, yes. But it wasn't what you wanted anyway (only
implemented a SQL cache for faster searching, interesting that almost
every "rewrite" attempt implements searching first)
> 3- If I tweak a custom profile not to have dev packages such as gcc,
> what kind of problems should I expect? Which packages from the base
> profile MUST exist? The idea is that the client machines should not
> be capable of compiling software.
I'd guess baselayout + it's deps + libc are the absolute minimum
(excluding baselayout-lite and other embedded solutions).
> 4- Any ideas on how the conf files should be handled?
Depends on your client nodes, if they are (almost) identical I'd just
sync them from a master node. If not it gets complicated.
Anyway, I hope you realize that your project doesn't only involve
hacking on portage, but rewriting almost all of it for the client part.
Actually I'd rather suggest you start from scratch (so you also make it
work completely without a tree), or wait for Brians rewrite in HEAD (not
a good idea though if you have a deadline). Server should be less of an
issue, mostly config tweaks there.
But as Donnie said, gentoo-portage-dev is the better list for this
discussion.
Marius
--
Public Key at http://www.genone.de/info/gpg-key.pub
In the beginning, there was nothing. And God said, 'Let there be
Light.' And there was still nothing, but you could see a bit better.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-22 14:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 1:58 [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22 2:12 ` Andrew Gaffney
2005-08-22 3:34 ` Donnie Berkholz
2005-08-22 10:05 ` Ivan Yosifov
2005-08-22 11:31 ` [gentoo-dev] " Duncan
2005-08-22 13:26 ` Ricardo Loureiro
2005-08-22 23:57 ` [gentoo-dev] " Duncan
2005-08-22 14:38 ` Marius Mauch [this message]
2005-08-22 15:35 ` [gentoo-dev] " Ricardo Loureiro
2005-08-22 16:57 ` Grobian
2005-08-22 17:49 ` Kristian Benoit
2005-08-22 20:39 ` Brian Harring
2005-08-23 16:25 ` Kristian Benoit
2005-08-23 17:22 ` Brian Harring
2005-08-23 17:27 ` Brian Harring
2005-08-23 22:58 ` Kristian Benoit
2005-08-25 0:50 ` [gentoo-dev] portage rewrite snapshot (was RFC - Gentoo on the Lab) Brian Harring
2005-08-23 16:45 ` [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22 20:41 ` Stephen Bennett
2005-08-23 16:28 ` Kristian Benoit
2005-08-23 17:19 ` Brian Harring
2005-08-23 16:34 ` Ricardo Loureiro
2005-08-23 17:28 ` Marius Mauch
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=20050822163811.3dcc8fde@andy.genone.homeip.net \
--to=genone@gentoo.org \
--cc=gentoo-dev@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