All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: poky@yoctoproject.org
Subject: Re: Distro policy ?
Date: Thu, 14 Apr 2011 13:28:22 -0700	[thread overview]
Message-ID: <4DA758E6.7040606@intel.com> (raw)
In-Reply-To: <20110414194445.9BCC5151F83@gemini.denx.de>

On 04/14/2011 12:44 PM, Wolfgang Denk wrote:
> HI,
>
> we're trying to build our own distribution based on Yocto 1.0.  We
> would like to push all modifications / extensions and our distro stuff
> upstream into the mainline repository, but we are not sure what is the
> best way to do this:
>
> So far we have put our distro-related changes into a separate layer
> but it seems that it was not so good idea: it looks like bitbake
> can't include files from one layer to another and we have to copy
> includes even if we don't want to change them.
>
Wolfgang,

I would like to get more details about which include files (.incs) you 
are needing to modify.  I know that there was some discussion at ELC 
this week about similar issues.  I also know that we have a "Layering 
Tools" item on the 1.1 feature list to address these issues.

> Putting our changes back into the main layer would be pretty trivial,
> but it appears that current tendency is to move all
> distribution-specific things to their respective layers (like the
> poky distro configuration itself was moved to the meta-yocto layer).
>
Correct, the core is supposed to be clean and distributions are supposed 
to be in layers.  Your layer can be linked to or hosted on the 
git.yoctoproject.org site if you would like. Pulling distro specific 
changes into core is not appropriate. If you have generic changes to 
core that would be appropriate to all distro, we would consider them.

> So, from the policy side I think we should go with our own layer.
> On the technical side I'm disappointed with this 'include' problem: I
> find it rather impractical to copy things we don't want to change and
> just want to use from one layer to another and then having to keep
> these in sync with mainline.
>
> What is the recommended way to address this issue?
>
For the short term, I think that you may need to deal with the copy 
issue, until we have tooling in place.

I know this is not the answer you wanted to hear right now, we know 
about the issue and are looking at it.

Sau!

> Best regards,
>
> Wolfgang Denk
>



  reply	other threads:[~2011-04-14 20:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-14 19:44 Distro policy ? Wolfgang Denk
2011-04-14 20:28 ` Saul Wold [this message]
2011-04-14 20:57   ` Chris Larson
2011-04-14 21:12     ` Martin Jansa
2011-04-14 21:19       ` Chris Larson
2011-04-20 22:39         ` Ilya Yanok
2011-04-20 22:56   ` Ilya Yanok
2011-04-14 21:43 ` Joshua Lock
2011-04-14 23:00   ` Matt Madison
2011-04-15 15:34     ` Richard Purdie
2011-04-20 22:44   ` Ilya Yanok

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=4DA758E6.7040606@intel.com \
    --to=saul.wold@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=wd@denx.de \
    /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.