From: Mike Looijmans <mike.looijmans@topic.nl>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: PRServer's problem
Date: Fri, 20 May 2016 12:00:25 +0200 [thread overview]
Message-ID: <573EE039.5090105@topic.nl> (raw)
In-Reply-To: <573C0726.3040402@windriver.com>
In addition, the introduction of PR server also increased the load on the
OpenPLi "feed" servers with a few terabytes per month. Luckily, bandwidth is
cheap nowadays :)
On 18-05-16 08:09, Robert Yang wrote:
> The PRServer bumps PR according to do_package's task hash, that
> causes it bumps *all* packages' PR when recipes like pseudo-native
> and rpm-native is changed. It is a very bad user experience when we
> run "smart/opkg upgrade" on running target, for example, when we apply
> a CVE patch to pseudo-native or rpm-native, or do some slight changes
> in their do_compile, "smart/opkg upgrade" will download/install *all*
> the packages since all of the packages' PR are bumped.
>
> Here are some rough suggestions to fix this problem, and please feel
> free to give your suggestions.
> 1) Do not use do_package's task for bumping PR, the easiest way
> is simulate manually bump PR -- only bump PR when the recipe
> itself's checksum is changed.
>
> 2) Add a new task for PRServer, redefine its task hash for bumping
> PR, for example, this task hash only considers RDEPENDS (no
> DEPENDS), and drop any native dependencies.
>
> I prefer the first way, and an alternative way maybe add a var so that
> the user can configure it:
> PR_CHECKSUM = "${BB_TASKHASH}" (current way)
> Or
> PR_CHECKSUM = "<recipe checksum>"
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Embedded Products
Eindhovenseweg 32-C, NL-5683 KH Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijmans@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
prev parent reply other threads:[~2016-05-20 16:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 6:09 PRServer's problem Robert Yang
2016-05-18 7:34 ` Joshua G Lock
2016-05-18 8:13 ` Robert Yang
2016-05-18 7:39 ` Martin Jansa
2016-05-18 8:03 ` Robert Yang
2016-05-18 9:20 ` Martin Jansa
2016-05-18 9:31 ` Robert Yang
2016-05-18 10:15 ` Martin Jansa
2016-05-19 2:33 ` Robert Yang
2016-05-19 3:10 ` Robert Yang
2016-05-19 9:45 ` Richard Purdie
2016-05-19 10:12 ` Robert Yang
2016-05-19 10:17 ` Richard Purdie
2016-05-20 2:27 ` Robert Yang
2016-05-19 10:37 ` Joshua G Lock
2016-05-19 11:10 ` Paul Eggleton
2016-05-19 8:47 ` Martin Jansa
2016-05-19 9:40 ` Richard Purdie
2016-05-19 9:45 ` Robert Yang
2016-05-19 10:24 ` Martin Jansa
2016-05-18 12:27 ` Sergey 'Jin' Bostandzhyan
2016-07-27 8:06 ` Robert Yang
2016-07-27 8:30 ` Sergey 'Jin' Bostandzhyan
2016-07-27 8:43 ` Robert Yang
2016-05-20 10:00 ` Mike Looijmans [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=573EE039.5090105@topic.nl \
--to=mike.looijmans@topic.nl \
--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