public inbox for gentoo-server@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ramon van Alteren <ramon@vanalteren.nl>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] Best practices in managing large server groups
Date: Wed, 23 May 2007 15:03:37 +0200	[thread overview]
Message-ID: <46543BA9.1000304@vanalteren.nl> (raw)
In-Reply-To: <46543382.1060707@gentoo.org>

Andrew Gaffney wrote:
> Ramon van Alteren wrote:
>> Well, basically he's right. Catalyst is a build tool that wraps all 
>> the stuff you need to do when building packages in a chroot, with 
>> some additional features
>> You don't need it.... it just saves time and a lot of work writing 
>> your own scripts to manage the environment, and it's semi-maintained.
>
> You have an odd definition of "maintained". Chris (catalyst lead) and 
> I (general code monkey) are actively working on catalyst. We just 
> don't care much about features that don't directly benefit release 
> building, since that's what catalyst's primary function is. If someone 
> asks for a feature that doesn't affect building releases and submits 
> code, we're very likely to throw it in.
Please, that's not what I meant, accept my apologies if that's what came 
across.

What I meant with semi-maintained is that it is maintained as an 
internal tool for building gentoo-releases and not as a general 
system-images buildtool.
Reading it again I should have said that more clearly, sorry.

Ramon

-- 
gentoo-server@gentoo.org mailing list



  reply	other threads:[~2007-05-23 13:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-20 18:29 [gentoo-server] Best practices in managing large server groups Charles Duffy
2007-05-20 20:20 ` Nicolas MASSE
2007-05-20 20:34   ` Charles Duffy
2007-05-20 21:25 ` Ramon van Alteren
2007-05-21  9:04   ` Ronan Mullally
2007-05-21 13:44     ` Thilo Bangert
2007-05-21 14:30       ` Ronan Mullally
2007-05-21 14:36         ` Arturo 'Buanzo' Busleiman
2007-05-21 14:53           ` Ronan Mullally
2007-05-21 15:01             ` Arturo 'Buanzo' Busleiman
2007-05-21 15:28               ` Christian Bricart
2007-05-21 15:54                 ` Arturo 'Buanzo' Busleiman
2007-05-22  4:19             ` Justin Cataldo
2007-05-22  4:59             ` Brian Kroth
2007-05-21 15:10     ` Karl Holz
2007-05-21 15:51       ` Ronan Mullally
2007-05-21 16:27         ` Ryan Gibbons
2007-05-21 17:29           ` Ronan Mullally
2007-05-21 17:35             ` Petteri Räty
2007-05-21 17:46               ` Ronan Mullally
2007-05-21 17:47             ` José Costa
2007-05-21 17:54               ` José Costa
2007-05-21 22:58           ` Karl Holz
2007-05-21 23:11 ` Ramon van Alteren
2007-05-22  5:10   ` Brian Kroth
2007-05-22 16:54   ` Charles Duffy
2007-05-22 17:23     ` Wendall Cada
2007-05-22 21:06       ` [gentoo-server] " Charles Duffy
2007-05-23  1:33         ` Wendall Cada
2007-05-23  7:37     ` [gentoo-server] " Ramon van Alteren
2007-05-23 12:28       ` Andrew Gaffney
2007-05-23 13:03         ` Ramon van Alteren [this message]
2007-05-23 13:46           ` Andrew Gaffney
2007-05-26  9:53       ` Thilo Bangert
2007-05-22 12:58 ` Tomasz Szymczak

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=46543BA9.1000304@vanalteren.nl \
    --to=ramon@vanalteren.nl \
    --cc=gentoo-server@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