All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: linux-yocto: ktypes/tiny and some questions along the way
Date: Wed, 14 Dec 2011 11:06:09 -0800	[thread overview]
Message-ID: <4EE8F3A1.3040109@linux.intel.com> (raw)
In-Reply-To: <4EE8EE57.1060608@windriver.com>

On 12/14/2011 10:43 AM, Bruce Ashfield wrote:
> On 11-12-14 01:07 PM, Darren Hart wrote:

Heavily trimmed down to the remaining points of discussion...

>> So what does that mean here? Well, I suggest we put all the sources in
>> standard (minus evil BSP patches obviously) and then create a ktype per
>> DISTRO definition:
> 
> And minus -rt at the moment.

Yes, sorry, I intended that, but didn't make that clear. Agreed.

>>
>> yocto/base
>> yocto/standard/base
>> yocto/standard/poky
>> yocto/standard/poky-rt
>> yocto/standard/poky-tiny
> 
> I'd want the distro not to be named in the branches, but yes,
> that looks ok to me.

Hrm, that's too bad. I really like the explicit coupling of the OE
distro definition to the linux-yocto branch. It helps reinforce the
concept of distro defined policy. I think I know where you are coming
from though.

> Yep, I'm not sold on a distro name, but if you change this to:
> 
>        yocto/base
>        yocto/standard/cfg (bad name, but I wanted something)
>        yocto/standard/rt
>        yocto/standard/tiny

How about:
        yocto/base
        yocto/standard/default
        yocto/standard/rt
        yocto/standard/tiny

"default" makes sense to me since, well, it is what we would use as the
default if no specification in made. Also, it's a shorter way of saying
"general purpose", which describes this policy/config fairly well.

> Then the tree is more of a common base ... they are just names after
> all! We already have 'yocto' in there, so that's enough specifics for
> my taste.
> 
> or we flip it around ...
> 
>     base
>     standard/yocto
>     standard/yocto-rt
>     standard/yocto-tiny
> 
> Which looks more like what you proposed, but without the double
> specific names.

It's less typing! I like less typing. But if we're going to do that, why
not:

     base
     standard/poky
     standard/poky-rt
     standard/poky-tiny

If you would prefer to keep the branches build-system/distro agnostic,
then I think the ideal would be:


     base
     standard/default
     standard/rt
     standard/tiny

And, it's even LESS typing! Fingers, wrists, and keyboards everywhere
will be thanking us. ;-)

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  reply	other threads:[~2011-12-14 19:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 22:52 linux-yocto: ktypes/tiny and some questions along the way Darren Hart
2011-12-09 23:09 ` Darren Hart
2011-12-10  1:05 ` Darren Hart
2011-12-10  6:53 ` Bruce Ashfield
2011-12-12  5:14 ` Bruce Ashfield
2011-12-12 23:17   ` Darren Hart
2011-12-14 16:59     ` Bruce Ashfield
2011-12-14 18:07       ` Darren Hart
2011-12-14 18:43         ` Bruce Ashfield
2011-12-14 19:06           ` Darren Hart [this message]
2011-12-14 19:13             ` Bruce Ashfield

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=4EE8F3A1.3040109@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.