чување c5daec393a536f1f384651abf458a1eae928a6ba
родитељ 0530df8bdd3e54920933ce0160046bd32a2c60eb
Аутор: Страхиња Радић <contact@strahinja.org>
Датум: Mon, 8 Aug 2022 22:19:53 +0200
Correct mkpk man section; additional explanation on a workaround
Signed-off-by: Страхиња Радић <contact@strahinja.org>
Diffstat:
измењених датотека: 2, додавања: 7(+), брисања: 5(-)
diff --git a/BUGS b/BUGS
@@ -21,7 +21,9 @@ Known bugs/Errata
* Once you finish compiling and installing everything, the build scripts won't
be fully functional for rebuilding packages from that point on, due to
sbase/ubase/9base utilities having only a subset of options of coreutils etc.
- You can revert this by uninstalling sbase, ubase and 9base.
+ This is only a concern if you want to customize the initial process and go
+ back and forth. Normally you would want to boot the installed system and use
+ mkpk(8) from that point on. Workaround: uninstall sbase, ubase and 9base.
* Running `mkpk info gcc` immediately after installation from bootstrap script
gives some errors. This is due to suckless tar having difficulties with tar
diff --git a/FAQ b/FAQ
@@ -30,13 +30,13 @@ A: What business? Use whatever software you like, or don't, it's up to you.
Q: How do I install a package?
A: cd / && xz -dc /pkg/some_pkg.tar.xz | tar -xf -
- or use mkpk(1)[1]:
+ or use mkpk(8)[1]:
mkpk install some_pkg
(when there is a tarball in /pkg).
Q: How do I uninstall a package?
A: cd / && xz -dc /pkg/some_pkg.tar.xz | tar -tf - | xargs rm
- or use mkpk(1):
+ or use mkpk(8):
mkpk uninstall some_pkg
Remove unwanted empty directories manually.
@@ -130,7 +130,7 @@ A: Quoting `man fakechroot`:
Obviously, for both reasons, this combination can't be used here.
- After the first boot, a packaging system mkpk(1) is used to build and install
+ After the first boot, a packaging system mkpk(8) is used to build and install
packages. It uses PRoot[5] to obtain root access necessary to create package
tarballs.
@@ -157,7 +157,7 @@ A: It didn't work well in tty under tmux. It only "works" (to a degree – with
vis back instead of vim if I or its authors figure out how to fix it.
Q: Why isn't there a graphical login and GNOME/Plasma etc?
-A: Surely you jest... ... ... No? Alright – because they are against the
+A: Surely you jest… … … No? Alright – because they are against the
fundamental principles behind Galeb.
If you give it a bit of thought, there is no reason at all for the existence
of graphical login programs (also called _display managers_, DMs) when there
