From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake task dependency stamp handling
Date: Sun, 07 Jan 2007 19:54:23 +0100 [thread overview]
Message-ID: <45A141DF.40409@dominion.kabel.utwente.nl> (raw)
In-Reply-To: <1168195833.5610.46.camel@localhost.localdomain>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
> I had some interesting thoughts regarding tasks and their timestamps.
> Bitbake's current method of dealing with timestamps walks the task
> digraph structure which only knows about a single .bb file. The result
> is if you change an earlier task, say do_patch, later tasks like
> do_compile would rerun. If you rebuild gtk, the rest of your system
> linking to gtk doesn't rebuild though.
>
> If we move away from the digraph which isn't really needed anymore,
> taskData has the complete dependency tree available to it and the option
> of rebuilding the whole system if you recompile gtk becomes possible.
>
> At face value this sounds really useful. I'd guess that almost every OE
> developer would find it insanely annoying in practise though?
Annoying, maybe, correct behaviour, yes. Option for local.conf?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFFoUHfMkyGM64RGpERApU6AKCHQ+UumH7Gw7rEbWbTb7fcW+wkzgCfRSbl
n/rabOe9dEZgkB4x617wYqo=
=jfo2
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-01-07 18:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 18:50 Bitbake task dependency stamp handling Richard Purdie
2007-01-07 18:54 ` Koen Kooi [this message]
2007-01-07 19:23 ` Marcin Juszkiewicz
2007-01-08 0:08 ` [Bitbake-dev] " Richard Purdie
2007-01-08 0:41 ` Matt Reimer
2007-01-08 7:15 ` Michael 'Mickey' Lauer
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=45A141DF.40409@dominion.kabel.utwente.nl \
--to=koen@dominion.kabel.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.