Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [thud][PATCH] Revert "OpkgPM: use --add-ignore-recommends to process BAD_RECOMMENDATIONS"
Date: Wed, 23 Oct 2019 11:41:05 +0300	[thread overview]
Message-ID: <20191023084104.GA4655@localhost> (raw)
In-Reply-To: <2e2b16b4-fff6-b84c-1f48-0e020a0f3629@gmail.com>

On Thu, Oct 17, 2019 at 12:21:11PM -0700, akuster808 wrote:
> On 10/17/19 11:42 AM, Denys Dmytriyenko wrote:
> > Thank you for this revert! I've been pulling my hair out past couple days 
> > figuring out why BAD_RECOMMENDATIONS stopped working for us. This fixed it.
> 
> What I find curious is that the offending commit has been in thud since
> July 29th and we are just now hearing about issues.
>...

The "Yocto is not a distribution, it is a tool to build distributions"
adds a layer between Yocto upstream and users that results in users
usually using old Yocto releases.

How large is actually the fraction of users who are creating their own 
distributions based on Yocto releases taken directly from upstream?

I would suspect most users are using 3rd party distributions provided by 
hardware vendors or companies like Wind River.

This adds quite a delay between a change being released in a Yocto 
stable release, and users actually using it.

When the distribution they are using is based on a thud release, new 
Yocto releases from that branch will only reach them when/if their 
distribution provider has updated and validated this change and made
a new release of the distribution.

Related, many of the Yocto user questions in various places tend to be 
for 2-3 year old Yocto releases. Often these sound like people just 
starting a new project with a distibution based on an old Yocto release.

> - armin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      parent reply	other threads:[~2019-10-23  8:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17 15:21 [thud][PATCH] Revert "OpkgPM: use --add-ignore-recommends to process BAD_RECOMMENDATIONS" Armin Kuster
2019-10-17 15:32 ` ✗ patchtest: failure for " Patchwork
2019-10-17 18:42 ` [thud][PATCH] " Denys Dmytriyenko
2019-10-17 19:21   ` akuster808
2019-10-17 20:01     ` Denys Dmytriyenko
2019-10-18 17:58       ` Alejandro Del Castillo
2019-10-18 21:18         ` akuster808
2019-10-21  6:08           ` Sean Nyekjaer
2019-11-22 15:15           ` Quentin Schulz
2019-10-23  8:41     ` Adrian Bunk [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=20191023084104.GA4655@localhost \
    --to=bunk@stusta.de \
    --cc=akuster808@gmail.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox