All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/5] network based PR service
Date: Thu, 19 May 2011 13:51:47 +0200	[thread overview]
Message-ID: <7AA87FA4-77D9-4D52-9D91-1BB909F268A6@dominion.thruhere.net> (raw)
In-Reply-To: <1305805104.3424.484.camel@rex>


Op 19 mei 2011, om 13:38 heeft Richard Purdie het volgende geschreven:

> On Thu, 2011-05-19 at 12:54 +0200, Koen Kooi wrote:
>> Op 19 mei 2011, om 12:29 heeft Lianhao Lu het volgende geschreven:
>> 
>>> From: Lianhao Lu <lianhao.lu@intel.com>
>>> 
>>> This series of 5 patches implemented the network based PR service and enabled 
>>> the poky to use it during the task do_package and do_package_write_xxx. By 
>>> using the network based PR service and the basichash for BB_SIGNATURE_HANDLER, 
>>> the poky user may not need to bump the PR manually everytime he/she changes 
>>> the recipe. The package will get automatically rebuilt and new revision number 
>>> reflecting the change will be included in the package feed.
>> 
>> Does it have a public/private mode? In the angstrom case, we only want
>> developers to 'submit' PR bumps and users only retrieve them.
> 
> It doesn't look like it but it wouldn't be hard to only submit PR
> changes if some kind of token was present.
> 
> The big question would be, if a user tried building something for which
> PR no record was on the server and didn't have submit privileges, what
> should the server return and how should the build behave? Hard error?
> 
> If its not a hard error, you are likely to run into local
> reproducibility issues and also conflicts with the server?

I would go for a warning on the client side and an error in the log in the server side. If the server people care enough they'll check the log for errors and add the missing info.

I think we need to give this a try and see what improvements we need.

regards,

Koen


  reply	other threads:[~2011-05-19 11:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 10:29 [PATCH 0/5] network based PR service Lianhao Lu
2011-05-19 10:29 ` [PATCH 1/5] Added the " Lianhao Lu
2011-05-19 10:29 ` [PATCH 2/5] conf/bitbake.conf: Added variables for " Lianhao Lu
2011-05-19 11:51   ` Richard Purdie
2011-05-19 10:29 ` [PATCH 3/5] classes/package(prserv).bbclass: Added PR service support Lianhao Lu
2011-05-19 11:54   ` Richard Purdie
2011-05-19 10:29 ` [PATCH 4/5] classes/package_xxx.class: " Lianhao Lu
2011-05-19 10:29 ` [PATCH 5/5] meta-yocto/local.conf.sample: Added PRSERV_HOST and PRSERV_PORT Lianhao Lu
2011-05-19 10:54 ` [PATCH 0/5] network based PR service Koen Kooi
2011-05-19 11:38   ` Richard Purdie
2011-05-19 11:51     ` Koen Kooi [this message]
2011-05-19 12:10       ` Richard Purdie
2011-05-19 11:01 ` Frans Meulenbroeks
2011-05-19 11:27   ` Frans Meulenbroeks
2011-05-19 11:35   ` Richard Purdie
2011-05-19 12:02     ` Frans Meulenbroeks
2011-05-19 12:22       ` Richard Purdie
2011-05-19 12:43         ` Frans Meulenbroeks
2011-05-19 13:13           ` Richard Purdie
2011-05-19 14:58             ` Mark Hatle
2011-05-19 12:02 ` Richard Purdie

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=7AA87FA4-77D9-4D52-9D91-1BB909F268A6@dominion.thruhere.net \
    --to=koen@dominion.thruhere.net \
    --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 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.