Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Br deps #83

Merged
merged 3 commits into from
Oct 23, 2019
Merged

Br deps #83

merged 3 commits into from
Oct 23, 2019

Conversation

NathanTP
Copy link
Contributor

This is another attempt at detecting if buildroot is up to date. See #21.

Hashing the rootfs doesn't work because each build changes the rootfs (probably a timestamp somewhere), so we have to manually try to track down all the dependencies.

The dependencies this pr tracks are:

  • br/buildroot-overlay
  • br/buildoot-config
  • the toolchain (linux headers and gcc version)
  • br/br.py

Notably absent is anything in br/buildroot/. I'm not sure how to reliably track what is/isn't up to date there. If you manually rebuild buildroot (e.g. 'cd br/buildroot && make'), marshal will notice and rebuild the children. I think in the rare cases that someone is modifying buildroot itself (rather than the config or overlays), they can just re-run make manually to pick up the changes.

@NathanTP NathanTP requested review from a0u and sagark October 22, 2019 20:16
@NathanTP NathanTP merged commit 66a8855 into dev Oct 23, 2019
@NathanTP NathanTP deleted the brDeps branch October 23, 2019 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants