| Summary: |
Suggested addition to explain how runtime virtual dependencies work |
| Product: |
[Documentation] Reference
|
Reporter: |
ulfalizer |
| Component: |
handbook | Assignee: |
Scott Rifenbark <srifenbark> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Undecided
|
CC: |
bluelightning, poky.doc.watcher, poky.watcher, srifenbark
|
| Version: |
2.2 | |
|
| Target Milestone: |
2.2 M4 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
03 August 2016: RESOLVED |
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Done (doc changes complete)
|
|---|
The meaning of VIRTUAL-RUNTIME_foo confused me a lot at first. I suggest adding the following note to the end of the PROVIDES glossary entry to explain what it means: Note { There is a corresponding mechanism for virtual runtime dependencies (packages), but it does not depend on any special functionality beyond ordinary variable assignments. For example, VIRTUAL-RUNTIME_dev_manager refers to the package of the component that manages the /dev directory. Setting the "preferred provider" for runtime dependencies is as simple as e.g. the following assignment in a configuration file: VIRTUAL-RUNTIME_dev_manager = "udev" } Cheers, Ulf