summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-11-10 10:28:25 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-11-25 15:24:17 +0000
commit684c35b7aa0898f95ab70a5982ef74ce98107d93 (patch)
tree7c6cb2ead87d121c32ed9d21943a28b54a0bb35d /documentation/adt-manual/adt-prepare.xml
parent8632404294eaa3464797cffc757add6b5d92b7dc (diff)
downloadpoky-684c35b7aa0898f95ab70a5982ef74ce98107d93.tar.gz
documentation: Changed all manual links to point to "latest"
There are many references to YP documentation throughout the YP manual set. They used to have hard-coded links to the current release (e.g. yoctoproject.org/docs/1.1 for Edison). This created a situation where if you went to a document on the website and clicked on a external reference to another manual, you would redirect to the current manual on the website. Really, you would want to go to the latest manual, which is one that is under development. Changing the links to "yoctoproject.org/docs/latest" makes the tip of master, which is used for devloping the next release, always have references to the manuals being developed and not back to the stable released set of manuals. This "latest" and "current" scheme for the links is not perfect. What has to happen when the latest set of the manuals freezes and becomes the next stable release, all the links in the docs will need to be changed from "latest" in the URL to the new release number. So for example, all the "latest" occurences would need to be changed to "1.2". Then for the next cycle as development begins again, the links need to be infused with "latest" again. (From yocto-docs rev: a234aef34303b07671da956de0e94b352797143e) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual/adt-prepare.xml')
-rw-r--r--documentation/adt-manual/adt-prepare.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 3fa59ec19e..098ff75ec7 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -164,9 +164,9 @@
164 <note> 164 <note>
165 The ADT Installer requires the <filename>libtool</filename> package to complete. 165 The ADT Installer requires the <filename>libtool</filename> package to complete.
166 If you install the recommended packages as described in the 166 If you install the recommended packages as described in the
167 "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#packages'>Packages</ulink>" 167 "<ulink url='http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html#packages'>Packages</ulink>"
168 section of 168 section of
169 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'> 169 <ulink url='http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html'>
170 The Yocto Project Quick Start</ulink>, then you will have libtool installed. 170 The Yocto Project Quick Start</ulink>, then you will have libtool installed.
171 </note> 171 </note>
172 172
@@ -330,9 +330,9 @@
330 To get the kernel and filesystem images, you either have to build them or download 330 To get the kernel and filesystem images, you either have to build them or download
331 pre-built versions. 331 pre-built versions.
332 You can find examples for both these situations in the 332 You can find examples for both these situations in the
333 "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#test-run'>A 333 "<ulink url='http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html#test-run'>A
334 Quick Test Run</ulink>" section of 334 Quick Test Run</ulink>" section of
335 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'> 335 <ulink url='http://www.yoctoproject.org/docs/latest/yocto-project-qs/yocto-project-qs.html'>
336 The Yocto Project Quick Start</ulink>. 336 The Yocto Project Quick Start</ulink>.
337 </para> 337 </para>
338 338
@@ -345,8 +345,8 @@
345 area - <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/'></ulink> 345 area - <ulink url='http://www.yoctoproject.org/downloads/yocto-1.1/machines/'></ulink>
346 and are ideal for experimentation within Yocto Project. 346 and are ideal for experimentation within Yocto Project.
347 For information on the image types you can build using the Yocto Project, see the 347 For information on the image types you can build using the Yocto Project, see the
348 "<ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" appendix in 348 "<ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html#ref-images'>Reference: Images</ulink>" appendix in
349 <ulink url='http://www.yoctoproject.org/docs/1.1/poky-ref-manual/poky-ref-manual.html'> 349 <ulink url='http://www.yoctoproject.org/docs/latest/poky-ref-manual/poky-ref-manual.html'>
350 The Yocto Project Reference Manual</ulink>. 350 The Yocto Project Reference Manual</ulink>.
351 </para> 351 </para>
352 352