aboutsummaryrefslogtreecommitdiffstats
path: root/posts
diff options
context:
space:
mode:
Diffstat (limited to 'posts')
-rw-r--r--posts/2022/packaging-for-arch-linux.rst13
1 files changed, 8 insertions, 5 deletions
diff --git a/posts/2022/packaging-for-arch-linux.rst b/posts/2022/packaging-for-arch-linux.rst
index 9b2e2f1..0b27eeb 100644
--- a/posts/2022/packaging-for-arch-linux.rst
+++ b/posts/2022/packaging-for-arch-linux.rst
@@ -229,7 +229,7 @@ files, that can be found in ``/usr/share/pacman/``:
b2sums=('THISISADUMMYCHECKSUM')
package() {
- make DESTDIR="$pgkdir" install -C $pkgname-$pkgver
+ make DESTDIR="$pkgdir" install -C $pkgname-$pkgver
}
To go through the essentials of this very minimalistic example, which assumes
@@ -407,11 +407,11 @@ provides separate install targets for the components).
'some-additional: for additional feature X'
)
- make DESTDIR="$pgkdir" install-scripts -C $pkgname-$pkgver
+ make DESTDIR="$pkgdir" install-scripts -C $pkgname-$pkgver
}
package_dummy-package-docs() {
- make DESTDIR="$pgkdir" install-docs -C $pkgname-$pkgver
+ make DESTDIR="$pkgdir" install-docs -C $pkgname-$pkgver
}
Binary repository management
@@ -566,7 +566,7 @@ builtin dependency resolution. Extending upon the example in `PKGBUILDs
}
package() {
- make DESTDIR="$pgkdir" install -C $pkgname-$pkgver
+ make DESTDIR="$pkgdir" install -C $pkgname-$pkgver
}
.. code:: sh
@@ -589,7 +589,7 @@ builtin dependency resolution. Extending upon the example in `PKGBUILDs
}
package() {
- make DESTDIR="$pgkdir" install -C $pkgname-$pkgver
+ make DESTDIR="$pkgdir" install -C $pkgname-$pkgver
}
If during build time ``libexample`` provided ``libexample.so.1``, the resulting
@@ -710,6 +710,9 @@ the following are some good starting points:
Update: I have fixed some typos. Thanks to Andreas Schleifer (Segaja) for
noticing them!
+ Update: I have fixed more typos. Thanks to `doesntthinkmuch
+ <https://www.reddit.com/user/doesntthinkmuch/>`_ for noticing them.
+
.. [1] I am excluding `flatpak <https://flatpak.org/>`_ and `snap
<https://snapcraft.io/>`_ in this article as they follow an app-store/
per-user installation paradigm. However, they relate to system's packaging