book-reader/desktopApp/packaging

Desktop package builds

Build Linux packages on the matching distro VM when testing manually:

cd ~/Reader
./gradlew :desktopApp:packageDeb -x test
./gradlew :desktopApp:packageRpm -x test
./gradlew :desktopApp:packageAur -x test

Build a Windows MSIX locally on Windows with the Windows SDK installed:

cd C:\Users\aryan\Desktop\Reader
.\gradlew.bat -PdesktopOnly=true -PdesktopAllowUnconfiguredStandardServices=true :desktopApp:packageReleaseMsix -x test

Copy the newest generated MSIX to your desktop:

$msix = Get-ChildItem .\desktopApp\build\compose\binaries\main-release\msix -Filter *.msix | Sort-Object LastWriteTime -Descending | Select-Object -First 1
Copy-Item -Force $msix.FullName "$env:USERPROFILE\Desktop\"

The MSIX task is separate from MSI packaging. It stages the release app image at desktopApp/build/msix/package, packages it with Windows SDK makeappx.exe, and writes the MSIX to:

desktopApp/build/compose/binaries/main-release/msix

For Microsoft Store submission, set the package identity values from Partner Center so AppxManifest.xml matches the reserved app identity:

.\gradlew.bat `
  -PdesktopOnly=true `
  -PdesktopMsixIdentityName=<Partner Center package identity name> `
  -PdesktopMsixPublisher=<Partner Center publisher CN> `
  -PdesktopMsixPublisherDisplayName=<Publisher display name> `
  :desktopApp:packageReleaseMsix -x test

If Windows SDK tools are not on PATH, pass them explicitly:

.\gradlew.bat `
  -PdesktopMakeAppxPath="C:\Program Files (x86)\Windows Kits\10\bin\<sdk-version>\x64\makeappx.exe" `
  :desktopApp:packageReleaseMsix -x test

Local signing is optional and separate:

.\gradlew.bat `
  -PdesktopMsixCertificatePath=C:\path\to\certificate.pfx `
  -PdesktopMsixCertificatePassword=<password> `
  :desktopApp:signReleaseMsix -x test

Recommended VM split:

• Ubuntu: ./gradlew :desktopApp:packageDeb -x test
• Fedora: ./gradlew :desktopApp:packageRpm -x test
• Arch: ./gradlew :desktopApp:packageAur -x test

Desktop-only Gradle invocations automatically skip the Android app module and the Android target in :shared, so desktop packaging does not require sdk.dir, Android SDK installation, or Android release signing values. You can force that mode for unusual command shapes with:

./gradlew -PdesktopOnly=true :desktopApp:packageDeb -x test

Desktop release values are centralized in gradle.properties:

desktopVersion=1.0.1
desktopPackageVersion=1.0.1
desktopAurPackageRelease=1

The AUR path is native Arch packaging. It does not wrap the .deb or .rpm. packageAur first creates a Linux app tarball, then generates an AUR worktree at:

desktopApp/build/aur/episteme-bin

On Arch, install/test the generated package with:

sudo pacman -U ~/Reader/desktopApp/build/aur/episteme-bin/*.pkg.tar.zst
episteme

For the OSS/offline flavor:

./gradlew :desktopApp:packageAur -PdesktopFlavor=oss -x test
sudo pacman -U ~/Reader/desktopApp/build/aur/episteme-oss-bin/*.pkg.tar.zst
episteme-oss

To inspect the AUR recipe manually instead:

./gradlew :desktopApp:prepareAurPackage -x test
cd ~/Reader/desktopApp/build/aur/episteme-bin
makepkg -si

For publish-ready AUR metadata, pass the release tarball URL:

./gradlew :desktopApp:prepareAurPackage \
  -PdesktopAurSourceUrl=https://example.com/releases/episteme-1.0.1-linux-x64.tar.gz \
  -x test

Then publish the generated PKGBUILD and .SRCINFO from the AUR directory.

The generated AUR recipes use license=('AGPL-3.0-only') and install the root LICENSE file into /usr/share/licenses/$pkgname/.

AUR repository setup

Create an account at:

https://aur.archlinux.org/register/

Add your public SSH key in the account settings, then confirm SSH works:

ssh aur@aur.archlinux.org

The command should authenticate and print AUR help text. It will not open a normal shell.

Create the package repos by cloning their not-yet-existing names:

git clone ssh://aur@aur.archlinux.org/episteme-bin.git
git clone ssh://aur@aur.archlinux.org/episteme-oss-bin.git

If a name already exists, inspect it first. If it is abandoned, follow the AUR orphan/adoption process instead of creating a duplicate package name.

For each release, extract the matching aur-<package>-<version>.tar.gz metadata archive from the GitHub release, copy PKGBUILD and .SRCINFO into the matching AUR clone, then commit and push:

tar -xzf aur-episteme-bin-1.0.1.tar.gz -C episteme-bin
cd episteme-bin
git add PKGBUILD .SRCINFO
git commit -m "Update to 1.0.1"
git push

Repeat the same flow for episteme-oss-bin.

CI release workflow

Desktop release in GitHub Actions builds desktop artifacts for standard and OSS flavors:

• Windows MSI
• Ubuntu/Debian DEB
• Fedora RPM
• Linux tarball used by AUR
• Direct Arch .pkg.tar.zst
• AUR metadata archives containing PKGBUILD and .SRCINFO
• SHA256SUMS.txt

Before running it, publish Pdfium once from a machine that has the ignored third_party/pdfium folders:

.\scripts\desktop\publish-pdfium-release.ps1 `
  -Repository Aryan-Raj3112/episteme `
  -Tag pdfium-desktop-v1

That release must contain:

pdfium-linux-x64-v8.zip
pdfium-win-x64-v8.zip

The desktop release workflow downloads those assets with:

.\scripts\desktop\download-pdfium.ps1 -Tag pdfium-desktop-v1

Required GitHub Secrets for standard desktop packages:

DESKTOP_FIREBASE_PROJECT_ID
DESKTOP_FIREBASE_WEB_API_KEY
DESKTOP_GOOGLE_OAUTH_CLIENT_ID
DESKTOP_GOOGLE_OAUTH_CLIENT_SECRET

MYAPP_RELEASE_STORE_FILE is not used by desktop packaging. Android is skipped for :desktopApp:* tasks.

AUR publishing still needs the two AUR repos:

episteme-bin
episteme-oss-bin

Upload the generated PKGBUILD and .SRCINFO from:

aur-episteme-bin-<version>.tar.gz
aur-episteme-oss-bin-<version>.tar.gz