public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: Max Arnold <lwarxx@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] small distros - setups and practices?
Date: Wed, 23 Apr 2008 10:03:10 +0800	[thread overview]
Message-ID: <20080423020310.GA6373@dev.local> (raw)
In-Reply-To: <1208883537.7206.11.camel@cgianelloni.quova.com>

On Tue, Apr 22, 2008 at 09:58:57AM -0700, Chris Gianelloni wrote:
> On Tue, 2008-04-22 at 20:18 +0800, Max Arnold wrote:
> > 1. Create small, task-oriented stage4 for fixed hardware configuration
> > 2. Deploy it to several machines (now looking for deployment variants and installers)
> > 3. Maintain it (updates)
> 
> This is rather funny, since I'm adding support for exactly this stuff to
> catalyst (and via other tools which will utilize catalyst).

Yes, synchronicity exists :)  Maybe I will be an early adopter?

> > I want special build host, where all binary targets are built. Its setup
> > should be easily repeatable by other developers (i.e. every task should be scripted,
> > without manual tweaks like 'chroot here and patch/emerge this'). Catalyst with
> > specs and overlays seems fine to me.
> 
> Sure.  In fact, I have 2 different "host types" right now, a "master"
> and a "build host" though they can reside on the same machine.

Which roles they have?

> > - Is it possible with catalyst to produce icremental binary updates (i.e. feed it with
> >   new snapshot and take set of updated packages as a result)? To me seems it is not.
> 
> Huh?  Have you ever looked at the package cache?
> 
> ls -l /var/tmp/catalyst/packages/stage4-i686-custom/All > ~/before.txt
> catalyst -f ~/stage4-i686-custom.spec
> ls -l /var/tmp/catalyst/packages/stage4-i686-custom/All > ~/after.txt
> diff -u ~/before.txt ~/after.txt
> 
> > - What about sequential stage4 generation without purging cache?
> 
> What about it?

You described my thoughts more clear (package cache, before.txt and after.txt)
My doubts was about using grp target.

> Well, I think that you need to spend a bit more time figuring out what
> catalyst can already do before asking for additional support.  Much of
> what you've asked here, catalyst already does.  ;]

Yes, that is what I'm currently doing :)
-- 
gentoo-catalyst@lists.gentoo.org mailing list



  reply	other threads:[~2008-04-23  2:04 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 [this message]
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
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=20080423020310.GA6373@dev.local \
    --to=lwarxx@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