APKBUILD examples:Subpackages: Difference between revisions

From Alpine Linux
m (added to Development Category)
(use cat template)
 
Line 1: Line 1:
Consider the following APKBUILD snippet:
Consider the following APKBUILD snippet:
pkgname="foo"
{{cat|foo/APKBUILD|<nowiki>...
subpackages="$pkgname-dev $pkgname-doc py-$pkgname:pysub libfoo"
pkgname="foo"
subpackages="$pkgname-dev $pkgname-doc py-$pkgname:pysub libfoo"
...</nowiki>}}


It will ...
It will ...

Latest revision as of 22:27, 16 September 2023

Consider the following APKBUILD snippet:

Contents of foo/APKBUILD

... pkgname="foo" subpackages="$pkgname-dev $pkgname-doc py-$pkgname:pysub libfoo" ...

It will ...

  • create the following 5 packages:
  1. foo (main)
  2. foo-dev (sub)
  3. foo-doc (sub)
  4. py-foo (sub)
  5. libfoo (sub)
  • using the following 5 package functions (respectively) to fill them with files:
  1. package(): will be provided by the user (and can make use of the $pkgdir variable).
  2. dev(): will be provided by abuild unless we override it, by providing our own dev() function (which can make use of the $subpkgdir variable).
  3. doc(): will be provided by abuild unless we override it, by providing our own doc() function (which can make use of the $subpkgdir variable).
  4. pysub(): will be provided by the user (and can make use of the $subpkgdir variable).
  5. libfoo(): will be provided by the user (and can make use of the $subpkgdir variable).