Gentoo Archives: gentoo-server

From: Andrew Gaffney <agaffney@g.o>
To: gentoo-server@l.g.o
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Wed, 23 May 2007 13:49:18
Message-Id: 465445C8.2060304@gentoo.org
In Reply to: Re: [gentoo-server] Best practices in managing large server groups by Ramon van Alteren
1 Ramon van Alteren wrote:
2 > Andrew Gaffney wrote:
3 >> Ramon van Alteren wrote:
4 >>> Well, basically he's right. Catalyst is a build tool that wraps all
5 >>> the stuff you need to do when building packages in a chroot, with
6 >>> some additional features
7 >>> You don't need it.... it just saves time and a lot of work writing
8 >>> your own scripts to manage the environment, and it's semi-maintained.
9 >>
10 >> You have an odd definition of "maintained". Chris (catalyst lead) and
11 >> I (general code monkey) are actively working on catalyst. We just
12 >> don't care much about features that don't directly benefit release
13 >> building, since that's what catalyst's primary function is. If someone
14 >> asks for a feature that doesn't affect building releases and submits
15 >> code, we're very likely to throw it in.
16 > Please, that's not what I meant, accept my apologies if that's what came
17 > across.
18 >
19 > What I meant with semi-maintained is that it is maintained as an
20 > internal tool for building gentoo-releases and not as a general
21 > system-images buildtool.
22 > Reading it again I should have said that more clearly, sorry.
23
24 That's *very* different from "semi-maintained" :)
25
26 --
27 Andrew Gaffney http://dev.gentoo.org/~agaffney/
28 Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
29 --
30 gentoo-server@g.o mailing list