All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Matsuzawa <tmatsuzawa@xevo.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: patching .bbclass files?
Date: Mon, 30 Jan 2017 06:38:55 +0000	[thread overview]
Message-ID: <CY1PR0101MB159426412AA0C373C827823BB64B0@CY1PR0101MB1594.prod.exchangelabs.com> (raw)
In-Reply-To: <CY1PR0101MB1594DCF757DEC39182FB3F8FB64B0@CY1PR0101MB1594.prod.exchangelabs.com>

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

Well, doing repo -diff and apply produced patch when I newly repo sync could work.


https://groups.google.com/forum/#!topic/repo-discuss/43juvD1qGIQ


________________________________
From: Takashi Matsuzawa
Sent: Monday, January 30, 2017 11:00 AM
To: yocto@yoctoproject.org
Subject: patching .bbclass files?


Hello Yocto
I am curious if there is a better way of doing this manually every time I re-synch to Yocto based BSP.

Say, I have a patch or customization I want to try on .bbclass files (instead of .bb or .bbappend, or the source files that are fetched.)
The reason for this is sometimes I want to try the latest fix to the BSP while building old versino of my image, or debbuging image by modifying the build system files.

I think by using .bbappend files I can try modification to the .bb file behaviros, but it does not for .bbclass files.
I could add slightly modified xxx.bbclass to my own layer so that it may override what is available in poky/meta/..., but it may mean I just duplicate a lot of bitbake related files in my layer for just a few lines of changes.

'repo' having a feature copying files when repositories are synched.  This may work for me?

Ideally, the poky and other remote gits have branches or releases that have the patches I want to try, or I should be using the latest releases that should include meaningful fixes already.
But it is not possible always.


[-- Attachment #2: Type: text/html, Size: 2502 bytes --]

      reply	other threads:[~2017-01-30  6:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-30  2:00 patching .bbclass files? Takashi Matsuzawa
2017-01-30  6:38 ` Takashi Matsuzawa [this message]

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=CY1PR0101MB159426412AA0C373C827823BB64B0@CY1PR0101MB1594.prod.exchangelabs.com \
    --to=tmatsuzawa@xevo.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.