Bug 10198 - Suggested new note in the DEPENDS glossary entry
Summary: Suggested new note in the DEPENDS glossary entry
Status: RESOLVED FIXED
Alias: None
Product: Reference
Classification: Documentation
Component: handbook (show other bugs)
Version: 2.2
Hardware: x86 Multiple
: Medium normal
Target Milestone: 2.2 M4
Assignee: Scott Rifenbark
QA Contact:
URL:
Whiteboard: 01 Sept 2016: IN PROGRESS REVIEW
Depends on:
Blocks:
 
Reported: 2016-08-31 07:55 UTC by ulfalizer
Modified: 2016-09-01 22:00 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Done (doc changes complete)

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 ulfalizer 2016-08-31 07:55:28 UTC 
Hello,

I'd put this between the two existing notes. It should hopefully avoid another common misunderstand and solidify what DEPENDS does.

  * One recipe having another recipe in DEPENDS does not by itself add any runtime
    dependencies between the packages produced by the recipes. However, as
    explained in the [RDEPENDS] glossary entry, runtime dependencies will often
    be created automatically, meaning [DEPENDS] alone is sufficient for most
    recipes.


Thanks,
Ulf
Comment 1 ulfalizer 2016-09-01 15:14:33 UTC 
Version 2:

  * One recipe having another recipe in DEPENDS does not by itself add any
    runtime dependencies between the packages produced by the two recipes.
    However, as explained in the [RDEPENDS] glossary entry, runtime
    dependencies will often be added automatically, meaning [DEPENDS] alone is
    sufficient for most recipes.
Comment 2 Scott Rifenbark 2016-09-01 21:26:35 UTC 
Ulf, 

See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-DEPENDS for the additional bullet in the note. 

Thanks, 
Scott
Comment 3 ulfalizer 2016-09-01 21:50:04 UTC 
Looks good to me.

Thanks,
Ulf
Comment 4 Scott Rifenbark 2016-09-01 22:00:01 UTC 
thanks, 

Setting to RESOLVED and putting the doc flag to "done."

Scott