aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorswirl <swurl@swurl.xyz>2022-01-27 12:43:54 -0500
committerGitHub <noreply@github.com>2022-01-27 12:43:54 -0500
commit79314ee67b0e7220d91d06908fd1370e8d9d6d57 (patch)
treeedc6fcc07c41d0b6a11975e15147a377c03c96aa
parent86b0637ef7b8f6f0b2a72e3c4db734fe1619b2f1 (diff)
parent1c982b01824d1b3892cd91208fe295d6816f352e (diff)
downloadPrismLauncher-79314ee67b0e7220d91d06908fd1370e8d9d6d57.tar.gz
PrismLauncher-79314ee67b0e7220d91d06908fd1370e8d9d6d57.tar.bz2
PrismLauncher-79314ee67b0e7220d91d06908fd1370e8d9d6d57.zip
Merge pull request #103 from redstrate/fix_rpm_build
Fix RPM build instructions
-rw-r--r--BUILD.md19
1 files changed, 14 insertions, 5 deletions
diff --git a/BUILD.md b/BUILD.md
index 1c06febb..d14f2941 100644
--- a/BUILD.md
+++ b/BUILD.md
@@ -47,16 +47,25 @@ If everything works correctly, the .deb will be next to the build script, in `Po
### Building a .rpm
-You don't need to install the build dependencies, as the script will use `dnf` to install them for you.
+Build dependencies are automatically installed using `dnf`, but you do need the `rpmdevtools` package (on Fedora)
+in order to fetch sources and setup your tree.
```
+cd ~
+# setup your ~/rpmbuild directory, required for rpmbuild to work.
+rpmdev-setuptree
+# note: submodules are not needed here, as the spec file will download the tarball instead
git clone https://github.com/PolyMC/PolyMC.git
-cd packages/rpm
-sudo dnf builddep ./polymec.spec
-rpmbuild -bb ./polymec.spec
+cd PolyMC/packages/rpm
+# install build dependencies
+sudo dnf builddep polymc.spec
+# download build sources
+spectool -g -R polymc.spec
+# now build!
+rpmbuild -bb polymc.spec
```
-The path to the rpm packages will be printed at the end of building
+The path to the rpm packages will be printed when the build is complete.
### Building from command line
You need a source folder, a build folder and an install folder.