Bug 10294 - Suggested addition re. empty packages in PACKAGES
Summary: Suggested addition re. empty packages in PACKAGES
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: 22 August 2016: RESOLVED
Depends on:
Blocks:
 
Reported: 2016-09-17 01:41 UTC by ulfalizer
Modified: 2016-09-22 23:21 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ulfalizer 2016-09-17 01:41:44 UTC
I suggest adding the following to the end of the PACKAGES glossary entry to
make the behavior for empty packages more discoverable. This was prompted by a
discussion on IRC
(http://lists.openembedded.org/pipermail/openembedded-core/2016-September/126569.html).

  Packages from PACKAGES that turn out empty (i.e. where none of the patterns
  in FILES_<pkg> match any files installed by [do_install]) are not generated,
  unless generation is forced through [ALLOW_EMPTY].


Cheers,
Ulf
Comment 1 Scott Rifenbark 2016-09-21 21:29:44 UTC
Ulf, 

See http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#var-PACKAGES. 

Thanks, 
Scott
Comment 2 ulfalizer 2016-09-22 04:53:04 UTC
Maybe

  Packages in the PACKAGES list that are empty...

would be a bit clearer. Other than that, it looks good to me.

Cheers,
Ulf
Comment 3 ulfalizer 2016-09-22 05:37:42 UTC
(In reply to comment #2)
> Maybe
> 
>   Packages in the PACKAGES list that are empty...
> 
> would be a bit clearer. Other than that, it looks good to me.

On a second thought, the original version doesn't sound too bad if you read the entire entry from the beginning, so I'm fine with it. :)

Cheers,
Ulf
Comment 4 Scott Rifenbark 2016-09-22 23:21:32 UTC
Ok, 

I think no changes are needed.  So, setting to RESOLVED and putting the doc flag to "done".

Thanks, 
Scott