From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-devel@lists.openembedded.org,
openembedded-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFC] Layers, PRINC and bbappends
Date: Thu, 16 May 2013 23:15:34 +0300 [thread overview]
Message-ID: <1368735334.18324.170.camel@ted> (raw)
In-Reply-To: <20130516092905.GG24809@jama.dyndns-home.com>
On Thu, 2013-05-16 at 11:29 +0200, Martin Jansa wrote:
> On Thu, May 16, 2013 at 10:10:45AM +0100, Paul Eggleton wrote:
> > On Thursday 16 May 2013 10:59:54 Martin Jansa wrote:
> > > On Thu, May 16, 2013 at 09:29:48AM +0100, Paul Eggleton wrote:
> > > > On Thursday 16 May 2013 08:31:33 Koen Kooi wrote:
> > > > > Removing layers is pretty much impossible, though.
> > > >
> > > > With PRINC gone would there be any other issue that would make removing
> > > > layers a problem?
> > >
> > > Does PR service really fix removing layers? I don't think so, if you add
> > > layer and checksum of foo is changed AUTOPR is incremented, but then you
> > > remove the layer and the checksum is unfortunately the same as what you
> > > had before AUTOPR will go backwards.
> >
> > Then I would have to say if that's not the behaviour you want we should change
> > it or at least make it optional to force it to always increment even if the
> > checksum is the same as a previous value.
>
> That won't work with multiple builders using the same PR server (I don't
> wont other builders to always increment PRAUTOs used in builds which
> populate official feed).
I just went and looked at the code and as far as I can tell PRServ
defaults to always incrementing upon a change. To get the other
behaviour you'd need nohist=False to PRData() in lib/prserv/db.py and I
can't see where that is set other than to the default :/. I'm tired and
perhaps missing something though.
Cheers,
Richard
next prev parent reply other threads:[~2013-05-16 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 7:36 [RFC] Layers, PRINC and bbappends Koen Kooi
2013-05-15 14:44 ` Paul Eggleton
2013-05-16 6:31 ` Koen Kooi
2013-05-16 8:29 ` Paul Eggleton
2013-05-16 8:59 ` [OE-core] " Martin Jansa
2013-05-16 9:10 ` Paul Eggleton
2013-05-16 9:29 ` Martin Jansa
2013-05-16 20:15 ` Richard Purdie [this message]
2013-05-15 20:33 ` Richard Purdie
2013-05-15 23:02 ` Paul Barker
2013-05-22 8:47 ` Paul Barker
2013-05-22 9:17 ` [OE-core] " Martin Jansa
2013-05-22 10:08 ` Paul Eggleton
[not found] ` <1369217654.6695.62.camel@phil-desktop.brightsign>
2013-05-23 2:50 ` Chris Larson
2013-05-27 12:07 ` Paul Barker
2013-05-16 6:23 ` Koen Kooi
2013-05-16 8:37 ` Paul Eggleton
2013-05-16 9:27 ` Martin Jansa
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=1368735334.18324.170.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=koen@dominion.thruhere.net \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@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