All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meeting 2010/03/02
Date: Wed, 3 Mar 2010 15:04:44 +0100	[thread overview]
Message-ID: <20100303140444.GP3206@jama> (raw)
In-Reply-To: <1267624062.2259.58.camel@rex>

On Wed, Mar 03, 2010 at 01:47:42PM +0000, Richard Purdie wrote:
> > I have considered converting some of the others to new staging.
> > Actually I even started it, but soon stopped with it for the following
> > reasons:
> > - the actual verification process is fairly cumbersome. (5) diff the 2
> > packaged-staging recipes (which I read as packaged-staging packages as
> > there are no packaged-staging recipes) is imho a pita)
> 
> It would be better to have some kind of automated way of doing this I
> agree. Its technically possible, just nobody has found the time needed
> to implement it. We're all volunteers as you point out.

Today while checking diff of pango and libxml I noticed that bumping
PR/INC_PR to target value before building it the old way helps a lot.

Even the binaries were a bit different when they were built from
different workdir because of PR (probably because of unstripped data in
workdir/image).

So now I first bump PR/INC_PR to target combination, then build without
BBCLASSEXTEND without rm_work inherit or -c build, backup workdir, make
BBCLASSEXTEND change, -c clean, -c build, and diff -rq workdir with
backuped version.

If it's different only in temp/run* temp/log* then it's great :). But
usually static libs are still a bit different but probably in harmless
way.

Regards,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         



  reply	other threads:[~2010-03-03 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 11:35 TSC Meeting 2010/03/02 Richard Purdie
2010-03-03 12:59 ` Frans Meulenbroeks
2010-03-03 13:26   ` Marcin Juszkiewicz
2010-03-03 13:47   ` Richard Purdie
2010-03-03 14:04     ` Martin Jansa [this message]
2010-03-03 14:28     ` Frans Meulenbroeks
2010-03-03 15:19       ` Richard Purdie
2010-03-05 17:47         ` Rolf Leggewie
2010-03-06 12:25           ` Frans Meulenbroeks

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=20100303140444.GP3206@jama \
    --to=martin.jansa@gmail.com \
    --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 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.