Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <alex.kanavin@gmail.com>
Cc: <majid.nasiry65@gmail.com>, <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] Backport some packages
Date: Mon, 31 Aug 2020 10:50:59 +0000	[thread overview]
Message-ID: <20200831105058.GE2162@korppu> (raw)
In-Reply-To: <CANNYZj_VWjmPswgd_yfgBSYWtQU9fh5CHRpmATtPJ_V9QqGGMw@mail.gmail.com>

Hi,

On Mon, Aug 31, 2020 at 11:32:56AM +0200, Alexander Kanavin wrote:
> The best is to ask your BSP supplier to provide a new version of the BSP
> that is compatible with recent Yocto versions.
> 
> Backporting userspace stuff is difficult or impossible.

For those who aren't afraid to digging deeper, it is possible to limit
the impact of BSP layers by e.g. restricting which recipes and bbappends
get applied in your product via BBMASK in distro config for example.
This enables much, much faster updates cycles since fixing one or two BSP recipes
for new yocto version is easier than waiting and possibly paying for a full
update with all bells and whistles.

In many cases users don't need all patches and changes provided in BSP SW layers.
In some cases they are even undesirable.

But yes, talking to BSP supplier(s) is a good start.

Cheers,

-Mikko

> Alex
> 
> On Mon, 31 Aug 2020 at 10:52, <majid.nasiry65@gmail.com> wrote:
> 
> > Hi
> > How can I backport some package (e.g php, cmake). My BSP only work in Krogoth
> > version and I want to use some new package (e.g from Sumo version).
> > I'm new in this stuffs. I don't know mybe the best way is I rewrite BSPs
> > and update whole project, anyway I don't know how can I do this too!
> >
> > Please help 
> >

> 

      reply	other threads:[~2020-08-31 10:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31  8:52 Backport some packages majid.nasiry65
2020-08-31  9:32 ` [yocto] " Alexander Kanavin
2020-08-31 10:50   ` Mikko Rapeli [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=20200831105058.GE2162@korppu \
    --to=mikko.rapeli@bmw.de \
    --cc=alex.kanavin@gmail.com \
    --cc=majid.nasiry65@gmail.com \
    --cc=yocto@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox