From f210ab4e2f332daff3cdbb148c5c2331f05e33ba Mon Sep 17 00:00:00 2001 From: =?utf8?q?Bj=C3=B8rn=20Forsman?= Date: Sun, 6 Feb 2011 20:02:04 +0100 Subject: [PATCH] docs: fix $(PKG)_SITE_METHOD names (UPPER CASE => lower case) MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit Currently, the documentation says $(PKG)_SITE_METHOD should have upper case names such as SVN or GIT, but the implementation only accepts lower case svn or git. This fixes the documentation. Signed-off-by: Bjørn Forsman Acked-by: Thomas Petazzoni Signed-off-by: Daniel Nyström Signed-off-by: Peter Korsgaard --- docs/buildroot.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/buildroot.html b/docs/buildroot.html index b755922c59..b766e410b6 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -1060,17 +1060,17 @@ $(eval $(call GENTARGETS,package,libfoo,host))
  • LIBFOO_SITE_METHOD may contain the method to fetch the package source code. It can either - be WGET (for normal FTP/HTTP downloads of - tarballs), SVN or GIT. When not + be wget (for normal FTP/HTTP downloads of + tarballs), svn or git. When not specified, it is guessed from the URL given in LIBFOO_SITE: git:// - and svn:// URLs will use the GIT - and SVN methods respectively. All other URL-types - will use the WGET method. So for example, in the + and svn:// URLs will use the git + and svn methods respectively. All other URL-types + will use the wget method. So for example, in the case of a package whose source code is available through Subversion repository on HTTP, one must - specifiy LIBFOO_SITE_METHOD=SVN. For SVN - and GIT methods, what Buildroot does is a + specifiy LIBFOO_SITE_METHOD=svn. For svn + and git methods, what Buildroot does is a checkout/clone of the repository which is then tarballed and stored into the download cache. Next builds will not checkout/clone again, but will use the tarball -- 2.30.2