public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Identifying inherit-only / usable profiles (round 2)
Date: Thu, 10 Mar 2005 11:27:40 -0500	[thread overview]
Message-ID: <1110472061.21812.28.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <20050310155333.622592c6@snowdrop>

[-- Attachment #1: Type: text/plain, Size: 908 bytes --]

On Thu, 2005-03-10 at 15:53 +0000, Ciaran McCreesh wrote:
> | Personally, I would like seeing a profile structure similar to this:
> | 
> | $type/$os/$arch/$ver/$sub
> 
> I'd like multiple inheritance in profiles too, or at least some kind of
> mixin style semi-multiple inheritance.

Actually, that would be very useful.  Be able to do things like have
both ".." and "../2004.3" in parent, so items from the parent in the
directory structure is read first, followed by the 2004.3 stuff.  There
are quite a few cascaded profiles that are nearly identical between
versions, with only a single change, but that are quite divergent from
the parent.  This would eliminate most of the duplication and redundancy
in them.

> Also, a pony.

How about a Great Dane that thinks he's a pony?

-- 
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-03-10 16:23 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 22:23 [gentoo-dev] Identifying inherit-only / usable profiles (round 2) Aaron Walker
2005-03-01 10:21 ` Aaron Walker
2005-03-01 14:47   ` Chris Gianelloni
2005-03-01 15:07     ` Aaron Walker
2005-03-07 18:42       ` Chris Gianelloni
2005-03-08 14:24         ` Mike Frysinger
2005-03-09  4:56           ` Aaron Walker
2005-03-09 16:46             ` Chris Gianelloni
2005-03-09 23:57               ` Jason Stubbs
2005-03-10  0:49                 ` Mike Frysinger
2005-03-10  0:50             ` Mike Frysinger
2005-03-10  1:41             ` Jerome Brown
2005-03-10 12:56               ` Aaron Walker
2005-03-10 15:49               ` Chris Gianelloni
2005-03-10 15:53                 ` Ciaran McCreesh
2005-03-10 16:27                   ` Chris Gianelloni [this message]
2005-03-13 18:17                     ` Jerome Brown
2005-03-13 20:19                       ` Chris Gianelloni
2005-03-13 22:05                         ` Martin Schlemmer
2005-03-14 14:43                           ` Mike Frysinger
2005-03-10 16:55                   ` Lina Pezzella
2005-03-30  9:27 ` Aaron Walker
2005-03-30 14:00   ` Chris Gianelloni
2005-04-01 18:50     ` Aaron Walker
2005-04-01 19:31       ` Mike Frysinger
2005-04-01 19:46         ` Chris Gianelloni
2005-04-01 21:02           ` Mike Frysinger
2005-04-02  6:15             ` Aaron Walker
2005-04-02  7:35               ` Jason Stubbs
2005-04-02 16:41                 ` Chris Gianelloni
2005-04-02 16:51                   ` Daniel Ostrow
2005-04-03  3:55                     ` Jason Stubbs

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=1110472061.21812.28.camel@cgianelloni.nuvox.net \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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