From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 6/7] docs/manual: update documentation about <pkg>_SOURCE, <pkg>_PATCH and <pkg>_EXTRA_DOWNLOADS
Date: Sun, 15 Mar 2015 17:45:51 +0100 [thread overview]
Message-ID: <5505B73F.3050702@openwide.fr> (raw)
In-Reply-To: <1425147313-17380-7-git-send-email-thomas.petazzoni@free-electrons.com>
Hi Thomas,
Le 28/02/2015 19:15, Thomas Petazzoni a ?crit :
> This commit updates the Buildroot manual for the variables used to
> indicate where to download the source code from:
>
> - It updates the description of <pkg>_SOURCE to make it clear that
> Buildroot assume that the tarball is hosted at <pkg>_SITE.
>
> - It updates the description of <pkg>_PATCH to indicate that not only
> file names (assumed to be hosted at <pkg>_SITE) can be used, but
> also full URLs. This allows to match with what the current code is
> doing.
>
> - It updates the description of <pkg>_EXTRA_DOWNLOADS to also
> indicate that full URLs are now accepted, following the change made
> in the previous commit.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
Reviewed-by: Romain Naour <romain.naour@openwide.fr>
> docs/manual/adding-packages-generic.txt | 32 ++++++++++++++++++--------------
> 1 file changed, 18 insertions(+), 14 deletions(-)
>
> diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
> index e3029ed..2e46d55 100644
> --- a/docs/manual/adding-packages-generic.txt
> +++ b/docs/manual/adding-packages-generic.txt
> @@ -204,18 +204,20 @@ information is (assuming the package name is +libfoo+) :
> +LIBFOO_VERSION = cb9d6aa9429e838f0e54faa3d455bcbab5eef057+ +
> +LIBFOO_VERSION = stable+
>
> -* +LIBFOO_SOURCE+ may contain the name of the tarball of
> - the package. If +HOST_LIBFOO_SOURCE+ is not specified, it
> - defaults to +LIBFOO_SOURCE+. If none are specified, then
> - the value is assumed to be
> - +libfoo-$(LIBFOO_VERSION).tar.gz+. +
> - Example: +LIBFOO_SOURCE = foobar-$(LIBFOO_VERSION).tar.bz2+
> +* +LIBFOO_SOURCE+ may contain the name of the tarball of the package,
> + which Buildroot will use to download the tarball from
> + +LIBFOO_SITE+. If +HOST_LIBFOO_SOURCE+ is not specified, it defaults
> + to +LIBFOO_SOURCE+. If none are specified, then the value is assumed
> + to be +libfoo-$(LIBFOO_VERSION).tar.gz+. + Example: +LIBFOO_SOURCE =
> + foobar-$(LIBFOO_VERSION).tar.bz2+
>
> * +LIBFOO_PATCH+ may contain a space-separated list of patch file
> - names, that will be downloaded from the same location as the tarball
> - indicated in +LIBFOO_SOURCE+, and then applied to the package source
> - code. If +HOST_LIBFOO_PATCH+ is not specified, it defaults to
> - +LIBFOO_PATCH+. Note that patches that are included in Buildroot
> + names, that Buildroot will download and apply to the package source
> + code. If an entry contains +://+, then Buildroot will assume it is a
> + full URL and download the patch from this location. Otherwise,
> + Buildroot will assume that the patch should be downloaded from
> + +LIBFOO_SITE+. If +HOST_LIBFOO_PATCH+ is not specified, it defaults
> + to +LIBFOO_PATCH+. Note that patches that are included in Buildroot
> itself use a different mechanism: all files of the form
> +<packagename>-*.patch+ present in the package directory inside
> Buildroot will be applied to the package after extraction (see
> @@ -246,10 +248,12 @@ information is (assuming the package name is +libfoo+) :
> +LIBFOO_SITE=/opt/software/libfoo.tar.gz+ +
> +LIBFOO_SITE=$(TOPDIR)/../src/libfoo/+
>
> -* +LIBFOO_EXTRA_DOWNLOADS+ lists a number of additional files that
> - Buildroot should download from +LIBFOO_SITE+ in addition to the main
> - +LIBFOO_SOURCE+ (which usually is a tarball). Buildroot will not do
> - anything with those additional files, except download files: it will
> +* +LIBFOO_EXTRA_DOWNLOADS+ is a space-separated list of additional
> + files that Buildroot should download. If an entry contains +://+
> + then Buildroot will assume it is a complete URL and will download
> + the file using this URL. Otherwise, Buildroot will assume the file
> + to be downloaded is located at +LIBFOO_SITE+. Buildroot will not do
> + anything with those additional files, except download them: it will
> be up to the package recipe to use them from +$(BR2_DL_DIR)+.
>
> * +LIBFOO_SITE_METHOD+ determines the method used to fetch or copy the
>
next prev parent reply other threads:[~2015-03-15 16:45 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 18:15 [Buildroot] [PATCH 0/7] Improvements to the download logic Thomas Petazzoni
2015-02-28 18:15 ` [Buildroot] [PATCH 1/7] linux: use the package infrastructure to download patches Thomas Petazzoni
2015-02-28 19:54 ` Baruch Siach
2015-03-15 14:59 ` Romain Naour
2015-03-15 15:14 ` Thomas Petazzoni
2015-03-15 15:58 ` Romain Naour
2015-03-22 15:15 ` Arnout Vandecappelle
2015-03-15 16:44 ` Romain Naour
2015-03-22 15:16 ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 2/7] pkg-generic: fix the logic showing the "Downloading" message Thomas Petazzoni
2015-03-15 16:44 ` Romain Naour
2015-03-22 15:19 ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 3/7] pkg-generic: take into account <pkg>_EXTRA_DOWNLOADS to display " Thomas Petazzoni
2015-03-15 16:44 ` Romain Naour
2015-03-22 15:20 ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 4/7] pkg-generic: refactor the "Downloading" message logic Thomas Petazzoni
2015-03-15 16:44 ` Romain Naour
2015-03-22 15:29 ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 5/7] pkg-generic: allow full URLs for <pkg>_EXTRA_DOWNLOADS Thomas Petazzoni
2015-03-15 16:45 ` Romain Naour
2015-03-22 15:33 ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 6/7] docs/manual: update documentation about <pkg>_SOURCE, <pkg>_PATCH and <pkg>_EXTRA_DOWNLOADS Thomas Petazzoni
2015-03-15 16:45 ` Romain Naour [this message]
2015-03-22 15:58 ` Arnout Vandecappelle
2015-02-28 18:15 ` [Buildroot] [PATCH 7/7] perl: use <pkg>_EXTRA_DOWNLOADS Thomas Petazzoni
2015-03-15 16:46 ` Romain Naour
2015-03-22 15:59 ` Arnout Vandecappelle
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=5505B73F.3050702@openwide.fr \
--to=romain.naour@openwide.fr \
--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