public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stuart Longland <redhatter@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] profiles
Date: Fri, 02 Sep 2005 00:22:17 +1000	[thread overview]
Message-ID: <43170E99.9060907@gentoo.org> (raw)
In-Reply-To: <4316DF4B.4060404@gentoo.org>

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

Stephen Bennett wrote:
> Stuart Longland wrote:
> 
>> So the profiles would become;
>>  
>>
>>> /usr/profiles/default-linux/mips:
>>> |- be -- Big Endian Systems
>>> |  |- n32 \__ Profile for any 64-bit voodoo
>>> |  |- n64 /
>>> |  |- ip22 -- SGI Indy, Indigo2 (R4k), Challenge S w/ o32
>>> |  |  |= n32 -- importing the ../n32 voodoo
>>> |  |  |- n64 -- importing the ../n64 voodoo
>>> |  |  '- 2.4 -- with kernel 2.6 stuff masked (for R4600)
>>> |  |
>>>
> Profiles don't do multiple inheritance. You'll either end up duplicating
> n32/n64 in all the relevant subprofiles, in which case why bother with
> be/n32, or the ip22/n32 profile won't inherit from ip22/, which kinda
> defeats the point, no?

That's a fly in the ointment, yes.  I spose that means removing the
toplevel n32 and n64 profiles.  This does mean duplication of files,
which is probably it's biggest downside -- but it gives us the greatest
flexibility IMHO.

In fact, there's an idea for profiles... why not have multiple
inheritance?  It'd be something to bring up with the portage devs I
think, but it may have some useful features.

Certainly though, at the very least, we should split according to
endianness and userland.  That way, CHOST and other vars can be set
correctly.
-- 
 ____                   _             Stuart Longland (a.k.a Redhatter)
/  _ \   ___    ___  __| |__  __   __ Gentoo Linux/MIPS Cobalt and Docs
- (_) \ /   \  ;   \(__   __)/  \ /  \                        Developer
 \    //  O _| / /\ \  | |  | /\ | /\ |
 /   / \   /__| /  \ \ | |  | \/ | \/ |
(___/   \____/|_;  |_| \_/   \__/ \__/ http://dev.gentoo.org/~redhatter

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-09-01 14:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 11:59 [gentoo-mips] IP30 hang on warm boot Aaron Walker
2005-08-11 20:05 ` Olivier Bornet
2005-08-11 22:22   ` Aaron Walker
2005-08-12  6:47     ` Olivier Bornet
2005-08-12 12:31       ` Aaron Walker
2005-08-13 10:14         ` Olivier Bornet
2005-08-30 15:18           ` [gentoo-mips] profiles Stephen P. Becker
2005-08-30 16:47             ` Curtis Phillips
2005-09-01  1:49               ` Stuart Longland
2005-09-01 11:00                 ` Stephen Bennett
2005-09-01 14:22                   ` Stuart Longland [this message]
2005-09-01 14:30                     ` Stephen Bennett
2005-09-01 12:12             ` Stephen Bennett
2005-09-03  2:05             ` Kumba

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=43170E99.9060907@gentoo.org \
    --to=redhatter@gentoo.org \
    --cc=gentoo-mips@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