From: Martin Jansa <martin.jansa@gmail.com>
To: "Stanislav Angelovič" <angelovic.s@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: Adding recipes to former meta-openembedded releases
Date: Fri, 24 May 2019 00:57:47 +0200 [thread overview]
Message-ID: <20190523225747.GC1421@jama> (raw)
In-Reply-To: <CAA9bybO-v4iJ8YcSDQVtmoopRY5YOjvhERUcQWjYh=1Omd--mQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]
On Fri, May 24, 2019 at 12:09:57AM +0200, Stanislav Angelovič wrote:
> Hi,
>
> I'm about to send a PR introducing a new recipe for sdbus-c++ library to
> meta-openembedded master. I'd also like to support previous releases -
> sumo, thud, warrior, where the recipe differs a little bit from current
> master version. Is it possible to send PR back-porting to branches
> representing those releases, or is the recommended practice to clone
> open-embedded and provide the recipes there on my own?
New recipes usually aren't added to released stable branches.
Providing the recipes on your own is reasonable approach, to keep it a
bit more organized you can use something like we do in webOS to have
separate layers for recipes/bbclasses backported from newer releases,
big advantage is that once you're ready to upgrade to newer release you
can just drop this whole layer from your builds and nothing should went
missing (instead of searching our layers for recipes which were
backported from somewhere).
See example in:
https://github.com/webosose/meta-webosose/tree/bf7f8d8a01a16b54f141c0a3441005a5b3ce4507/meta-webos-backports
Regards,
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
prev parent reply other threads:[~2019-05-23 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 22:09 Adding recipes to former meta-openembedded releases Stanislav Angelovič
2019-05-23 22:57 ` Martin Jansa [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=20190523225747.GC1421@jama \
--to=martin.jansa@gmail.com \
--cc=angelovic.s@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.