From: Richard Purdie <richard.purdie@linuxfoundation.org>
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 12:35:06 +0100 [thread overview]
Message-ID: <1305804906.3424.480.camel@rex> (raw)
In-Reply-To: <BANLkTimrb+YjVGP_eh_i8nDunvye0vApJA@mail.gmail.com>
On Thu, 2011-05-19 at 13:01 +0200, Frans Meulenbroeks wrote:
> What should I do to either disable this for some recipes, or use a
> different (private) server?
> We do not wish to rely on an external server for proprietary recipes (or for
> recipes for which we made a local change in an overlay).
> How is this case handled?
This could be handled by doing things like setting:
PRSERV_HOST_pn-myprivaterecipe = "somelocalhost"
or
PRSERV_HOST_pn-myprivaterecipe = ""
to disable it.
One thing we lack is a good way to apply changes like this, only if code
is within a given layer. Even in that case, it should be possible with
anonymous python to look at the location of the current .bb file and
then conditionally set these variables as appropriate to the right
server.
Certainly this needs to be thought about and documented but I think
there are ways to do it.
Cheers,
Richard
next prev parent reply other threads:[~2011-05-19 11:38 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
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 [this message]
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=1305804906.3424.480.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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