PKGBUILD


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52

# Maintainer: sunnysab <i@sunnysab.cn>
pkgname=intel-xpu-smi-bin
pkgver=1.3.5
pkgrel=1
# The build version part from the filename
_buildver=20251216.170635.605ff78d.u24.04
pkgdesc="Intel XPU SMI - CLI tool for Intel XPU Manager (Binary, Daemon-less)"
arch=('x86_64')
url="https://github.com/intel/xpumanager"
license=('MIT')

# Core dependencies required for hardware access and firmware updates
depends=(
    'intel-compute-runtime'
    'level-zero-loader'
    'igsc'               # Required for libigsc.so.0
    'intel-media-driver'
    'onevpl-intel-gpu'
)

# Conflicts with the daemon-based manager as per Intel documentation
conflicts=('intel-xpumanager' 'intel-xpumanager-bin' 'intel-xpu-smi')
provides=('intel-xpu-smi' 'libxpum.so')

# Use the official GitHub release URL
source=("https://github.com/intel/xpumanager/releases/download/v${pkgver}/xpu-smi_${pkgver}_${_buildver}_amd64.deb")

# IMPORTANT: Run 'updpkgsums' to generate real checksums before AUR submission
sha256sums=('21c82a890f5712a659d3c31eaa42bc6c2c6c0d08a677d57fbc67eda0a54c8934')

package() {
    msg2 "Extracting data.tar.gz..."
    # Extract data.tar.gz from the deb package
    bsdtar -O -xf "${srcdir}/xpu-smi_${pkgver}_${_buildver}_amd64.deb" data.tar.gz | bsdtar -C "${pkgdir}" -xvf -

    # --- Fix 1: Library Paths ---
    # The deb package likely puts libs in /usr/lib/x86_64-linux-gnu (Ubuntu style).
    # We must move them to /usr/lib for Arch Linux.
    if [ -d "${pkgdir}/usr/lib/x86_64-linux-gnu" ]; then
        msg2 "Moving libraries to /usr/lib..."
        mv "${pkgdir}/usr/lib/x86_64-linux-gnu/"* "${pkgdir}/usr/lib/"
        rmdir "${pkgdir}/usr/lib/x86_64-linux-gnu"
    fi

    # --- Cleanup ---
    # Remove unnecessary documentation if you prefer a cleaner package (Optional)
    # rm -rf "${pkgdir}/usr/share/doc"

    # Note: Unlike the Manager package, SMI is daemon-less.
    # It does NOT need systemd services, sysusers, or tmpfiles configuration.
    # It runs directly as the invoking user (usually root via sudo).
}