Revisiting bitbake stamp handling

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

For a number of features in OE (e.g packaged-staging, rm_work) a change to bitbake stamp
handling would make things a lot easier. As I understand it bitbake currently does for
'bitbake foo -c compile':

if(dependency stamps are missing OR depency stamps have newer mtime) then start from scratch

For rm_work we want to remove the do_unpack upto do_install stamps, but leave do_fetch and
do_package_write* and for packaged-staging we want to only create a do_populate_staging
stamps. So 'bitbake foo -c compile' would only do:

if(depency stamps have newer mtime) then start from scratch

this has implications for do_clean and do_rebuild, and possibly other things. Since this
looks to good to be true, I want to know what else might break and how we could solve that
when implementing this. This just a gedankenexperiment for now, so bitbake hackers can
relax now :)

regards,

Koen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFG8Ad/MkyGM64RGpERArW7AKCY91yVx8se1jUej3FiZyVRTpuZVgCghoca
n9KyhcAJ4a4VhBvxh360wto=
=152E
-----END PGP SIGNATURE-----