Bug 7827 - Handle if bitbake server code changes when memory resident
Summary: Handle if bitbake server code changes when memory resident
Status: NEW
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: 1.8
Hardware: All Multiple
: Low enhancement
Target Milestone: Future
Assignee: Unassigned
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-05-29 15:49 UTC by Paul Eggleton
Modified: 2026-07-16 15:18 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-05-29 15:49:27 UTC 
If you use oe-init-build-env-memres and you're making changes to bitbake server code or you switch branches, unless you explicitly restart the bitbake server  it will still be running and won't match the code on disk, leading to much confusion and possibly errors. If practical it would be nice if we could use inotify to at least detect such changes show a warning, or potentially even stop or restart the bitbake server in response.
Comment 1 Stephen K Jolley 2017-09-14 15:16:00 UTC 
Still a valid idea.