From cd24f443944bd74d53c3ef931ed7e919e743e826 Mon Sep 17 00:00:00 2001 From: Martin Jansa Date: Tue, 30 Nov 2010 08:49:08 +0100 Subject: usermanual: update info with SRCPV, in recipe SRCREV and remove sane-srcdates Signed-off-by: Martin Jansa --- docs/usermanual/chapters/common_use_cases.xml | 20 ++++---------------- 1 file changed, 4 insertions(+), 16 deletions(-) (limited to 'docs') diff --git a/docs/usermanual/chapters/common_use_cases.xml b/docs/usermanual/chapters/common_use_cases.xml index 21140472be..61b4963f37 100644 --- a/docs/usermanual/chapters/common_use_cases.xml +++ b/docs/usermanual/chapters/common_use_cases.xml @@ -55,17 +55,6 @@ PREFERRED_VERSION_linux-omap1_omap5912osk ?= "2.6.18+git" PREFERRED_VERSION_linux-openzaurus ?= "2.6.17" - - - To get more stable build it is good to make use of - sane-srcdates.inc file which contain working SRCDATE for many of - floating recipes. -require conf/distro/include/sane-srcdates.inc - It also should have global SRCDATE - value set (format is ISO date: YYYYMMDD): -SRCDATE = "20061014" - - @@ -152,12 +141,11 @@ SRCDATE = "20061014" prevent random breakage in OE at the most inopportune time for all OE users. Here is how to do that properly. - for svn: add 'PV = "1.1+svnr${SRCREV}"' to your bb file. - for cvs: add 'PV = "1.1+cvs${SRCREV}"' to your bb file. + for svn: add 'PV = "1.1+svnr${SRCPV}"' to your bb file. + for git: add 'PV = "1.1+gitr${SRCPV}"' to your bb file. + for cvs: add 'PV = "1.1+cvs${SRCPV}"' to your bb file. - Accompany either with an entry to conf/distro/include/sane-srcrevs.inc for a revision that you know - builds successfully. It is also common to define the stable SRCREV - for your package directly in the package recipe. + Accompany with stable SRCREV for your package directly in the package recipe. If you really absolutely have to follow the latest commits, you can do that by adding -- cgit 1.2.3-korg