Commit b6009b94 authored by Thomas Petazzoni's avatar Thomas Petazzoni Committed by Peter Korsgaard
Browse files

docs/manual: update to mention the multiple patches support 



After the modification of the <pkg>_PATCH semantic, let's update the
documentation accordingly.

Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: default avatarPeter Korsgaard <jacmet@sunsite.dk>
parent e260a2d9

docs/manual/adding-packages-generic.txt

+10 −7
Original line number Diff line number Diff line
@@ -156,14 +156,17 @@ information is (assuming the package name is +libfoo+) : 
  +packagename-$(LIBFOO_VERSION).tar.gz+. +

  Example: +LIBFOO_SOURCE = foobar-$(LIBFOO_VERSION).tar.bz2+



* +LIBFOO_PATCH+ may contain the name of a patch, that will be

  downloaded from the same location as the tarball indicated in

  +LIBFOO_SOURCE+. 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

* +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

  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

  xref:patch-policy[patching a package]).

  xref:patch-policy[patching a package]). Finally, patches listed in

  the +LIBFOO_PATCH+ variable are applied _before_ the patches stored

  in the Buildroot package directory.



* +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