Bug 8301

Summary: Include new PACKAGE_FEED_PREFIX description
Product: [Documentation] Reference Reporter: Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez>
Component: handbookAssignee: Scott Rifenbark <srifenbark>
Status: VERIFIED FIXED QA Contact: Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu>
Severity: normal    
Priority: Medium CC: alexander.kanevskiy, bluelightning, bogdanx.a.voiculescu, poky.doc.watcher, poky.watcher, srifenbark
Version: 1.8   
Target Milestone: 2.0   
Hardware: All   
OS: Multiple   
Whiteboard: 06 Oct 2015: IN PROGRESS REVIEW
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Done (doc changes complete)

Description Leonardo Sandoval Gonzalez 2015-09-15 15:49:41 UTC
When creating package feeds, there is new variable with helps constructing URLs (PACKAGE_FEED_PREFIX). The following patch includes the feature and should be described on the reference manual

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=338c3257f60e99c1fd101d5010daea4099eb1d0e
Comment 1 Scott Rifenbark 2015-09-22 14:45:46 UTC
Estimating at 1.0 days.

Scott
Comment 2 Scott Rifenbark 2015-09-22 15:10:55 UTC
Added myself to the CC list.
Comment 3 Leonardo Sandoval Gonzalez 2015-10-05 21:28:22 UTC
Scott,

new patch sent to the mailing list regarding package feeds:

http://lists.openembedded.org/pipermail/openembedded-core/2015-October/111297.html

Let's wait for Paul (and community) for possible comments.
Comment 4 Scott Rifenbark 2015-10-06 17:20:01 UTC
Hi, 

Thanks for the clear example and information.  I have added descriptions for the three new PACKAGE_FEED_* variables and I used your nice example as part of the descriptions.  Note that I repeated the example for each of the variables in the reference.  If this part of the manual were not a pure reference area of the variables I would have not repeated the example, but rather would have leveraged off of a single example.  However, I think this level of redundancy in a glossary where each variable is somewhat self-contained is acceptable. 

Let me know what you think of the descriptions and if you find anything wrong I will correct it. 

Here are the links for review:

 * http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-PACKAGE_FEED_ARCHS

* http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-PACKAGE_FEED_BASE_PATHS

* http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-PACKAGE_FEED_URIS

Thanks, 
Scott
Comment 5 Leonardo Sandoval Gonzalez 2015-10-06 19:09:37 UTC
(In reply to comment #4)
> Hi, 
> 
> Thanks for the clear example and information.  I have added descriptions for
> the three new PACKAGE_FEED_* variables and I used your nice example as part
> of the descriptions.  Note that I repeated the example for each of the
> variables in the reference.  If this part of the manual were not a pure
> reference area of the variables I would have not repeated the example, but
> rather would have leveraged off of a single example.  However, I think this
> level of redundancy in a glossary where each variable is somewhat
> self-contained is acceptable. 
> 
> Let me know what you think of the descriptions and if you find anything
> wrong I will correct it. 

Scott, looks good to me. Thanks for documenting these.
Adding Paul into the CC list.

> 
> Here are the links for review:
> 
>  *
> http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-
> PACKAGE_FEED_ARCHS
> 
> *
> http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-
> PACKAGE_FEED_BASE_PATHS
> 
> *
> http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-
> PACKAGE_FEED_URIS
> 
> Thanks, 
> Scott
Comment 6 Scott Rifenbark 2015-10-07 14:01:58 UTC
Thanks, 

Setting to RESOLVED/FIXED and putting the doc flag to "Done."

Scott