From: Nathan Lynch <ntl@pobox.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] docs: update LIBFOO_SITE to describe use of filesystem paths
Date: Sun, 17 Jun 2012 16:53:59 -0500 [thread overview]
Message-ID: <1339970041-17398-2-git-send-email-ntl@pobox.com> (raw)
In-Reply-To: <1339970041-17398-1-git-send-email-ntl@pobox.com>
Buildroot supports the use of local filesystem paths in LIBFOO_SITE
since the 2011.11 release, but this is not documented in the manual.
Fix this and slightly reword the surrounding doucmentation
accordingly.
Signed-off-by: Nathan Lynch <ntl@pobox.com>
---
docs/manual/adding-packages-gentargets.txt | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/docs/manual/adding-packages-gentargets.txt b/docs/manual/adding-packages-gentargets.txt
index cfcee8c..918580e 100644
--- a/docs/manual/adding-packages-gentargets.txt
+++ b/docs/manual/adding-packages-gentargets.txt
@@ -156,13 +156,18 @@ The list of variables that can be set in a +.mk+ file to give metadata
package directory inside Buildroot will be applied to the package
after extraction.
-* +LIBFOO_SITE+ may contain the Internet location of the package. It
- can either be the HTTP, FTP or SCP location of a tarball, or the URL
- of a Git, Subversion, Mercurial or Bazaar repository (see
- +LIBFOO_SITE_METHOD+ below). +
- SCP URLs should be of the form +scp://[user@]host:filepath+. Note
- that filepath is relative to the user's home directory, so you may want
- to prepend the path with a slash for absolute paths:
+* +LIBFOO_SITE+ provides the location of the package, which can be a
+ URL or a local filesystem path. HTTP, FTP and SCP are supported URL
+ types for retrieving package tarballs. Git, Subversion, Mercurial,
+ and Bazaar are supported URL types for retrieving packages directly
+ from source code management systems. A filesystem path may be used
+ to specify either a tarball or a directory containing the package
+ source code. See +LIBFOO_SITE_METHOD+ below for more details on how
+ retrieval works. +
+ Note that SCP URLs should be of the form
+ +scp://[user@]host:filepath+, and that filepath is relative to the
+ user's home directory, so you may want to prepend the path with a
+ slash for absolute paths:
+scp://[user@]host:/absolutepath+. +
If +HOST_LIBFOO_SITE+ is not specified, it defaults to
+LIBFOO_SITE+. If none are specified, then the location is assumed
@@ -172,6 +177,8 @@ The list of variables that can be set in a +.mk+ file to give metadata
+LIBFOO_SITE=http://www.libfoosoftware.org/libfoo+ +
+LIBFOO_SITE=http://svn.xiph.org/trunk/Tremor/+ +
+LIBFOO_SITE=git://github.com/kergoth/tslib.git+
+ +LIBFOO_SITE=/opt/software/libfoo.tar.gz+
+ +LIBFOO_SITE=$(TOPDIR)/../src/libfoo/+
* +LIBFOO_SITE_METHOD+ may contain the method to fetch the package
source code. It can either be +wget+ (for normal FTP/HTTP downloads
--
1.7.10.2
next prev parent reply other threads:[~2012-06-17 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 21:53 [Buildroot] [PATCH 0/3] Document use of local sources for packages Nathan Lynch
2012-06-17 21:53 ` Nathan Lynch [this message]
2012-06-17 21:54 ` [Buildroot] [PATCH 2/3] docs: rework LIBFOO_SITE_METHOD documentation Nathan Lynch
2012-06-17 21:54 ` [Buildroot] [PATCH 3/3] docs: describe "file" and "local" methods in LIBFOO_SITE_METHOD Nathan Lynch
2012-06-18 6:50 ` [Buildroot] [PATCH 0/3] Document use of local sources for packages Thomas Petazzoni
2012-06-30 19:07 ` Arnout Vandecappelle
2012-07-02 5:33 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1339970041-17398-2-git-send-email-ntl@pobox.com \
--to=ntl@pobox.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox