search

crops / poky-container

A container image that is able to run bitbake/poky. It has helpers to create users and groups within the container. This is so that the output generated in the container will be readable by the user on the host.
GNU General Public License v2.0
206 stars 94 forks source link

README.md: update link to YP docs #13

Closed gizero closed 7 years ago

gizero commented 7 years ago

Update Yocto Project documentation link to point to latest released Quick Start Guide (2.2.1).

rewitt1 commented 7 years ago

That's a good point. If we want to stick with released versions, then I think "current" would work instead of "latest".

On Apr 12, 2017 10:24 PM, "Andrea Galbusera" notifications@github.com wrote:

@gizero commented on this pull request.

In README.md https://github.com/crops/poky-container/pull/13#discussion_r111313622:

@@ -63,4 +63,4 @@ point. pokyuser@3bbac563cacd:/workdir$


At this point you should be able to follow the same instructions as described
-  in https://www.yoctoproject.org/docs/2.1/yocto-project-qs/yocto-project-qs.html#releases.
+  in https://www.yoctoproject.org/docs/2.2.1/yocto-project-qs/yocto-project-qs.html#releases.

Thought you wanted to reference the most recent released documentation here: latest links point to ongoing builds of documentation. They may reference, as is the case these days with 2.3, a yet unreleased version of the Yocto project. If we don't mind this could appear misleading to newcomers (people who probably could benefit most of this link indeed), I agree using latest is definitely more self-maintaining.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/crops/poky-container/pull/13#discussion_r111313622, or mute the thread https://github.com/notifications/unsubscribe-auth/ADfcu0mwvR4ZH7MpsO7Uvm_QbxQRSKK0ks5rvbGLgaJpZM4M2pGd .

gizero commented 7 years ago

Right! Didn't know about current. That's exactly what we need... I'll send an updated PR

gizero commented 7 years ago

Closing this and re-sending as a new PR ( #15 ) with a single patch and "Signed-off by"