Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [PATCH] .gitignore: add /bitbake to the ignore list for external distributions
Date: Wed, 9 May 2012 09:45:53 -0500	[thread overview]
Message-ID: <4FAA8321.707@windriver.com> (raw)
In-Reply-To: <1336573316.5602.68.camel@phil-desktop>

On 05/09/2012 09:21 AM, Phil Blundell wrote:
> On Wed, 2012-05-09 at 08:46 -0500, Jason Wessel wrote:
>> External distributions based on the oe-core will typically include
>> bitbake in the top level directory.  The idea is to make it easy
>> for external distributions to easily assemble a distribution
>> with a pristine version of oe-core, add avoid the git untracked messages:
> 
> Presumably any non-trivial external distribution is going to include
> other metadata as well, in which case they're going to have to
> edit .gitignore for themselves anyway.  So it doesn't really seem as
> though having bitbake be mentioned there in oe-core buys much.
> 
> On the other hand, actually moving bitbake inside the oe-core repository
> seems like an idea which might have some merit.  It's not obvious that
> having it in its own tree really achieves anything other than making
> release engineering slightly more difficult.


It appeared to me that the bitbake was maintained by an entirely different group of people, but oe-core is completely tied to bitbake.  It might always be the case that it will still be a separate repository and perhaps this is a side effect of how the poky git vs the development of the Yocto Project are maintained, with the other work flow being to assemble a distribution.

Technically the poky git has the same issue, but you do not see it because of the way it is managed.  Ideally I would have liked to see that change as well, but I understand it is done that way for simplicity vs using git submodules or subgit trees with a tool like repo or others.

It would be interesting to hear a few more view points on this topic.

Jason.



  reply	other threads:[~2012-05-09 14:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 13:46 [PATCH] .gitignore: add /bitbake to the ignore list for external distributions Jason Wessel
2012-05-09 13:58 ` Koen Kooi
2012-05-09 14:07   ` Marko Lindqvist
2012-05-09 16:10     ` Philip Balister
2012-05-09 16:14       ` Jason Wessel
2012-05-10  5:26       ` Khem Raj
2012-05-09 14:15   ` Jason Wessel
2012-05-09 14:21 ` Phil Blundell
2012-05-09 14:45   ` Jason Wessel [this message]
2012-05-09 15:00     ` Koen Kooi
2012-05-09 15:54   ` Richard Purdie

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=4FAA8321.707@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philb@gnu.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