Arch Linux User Repository

Which package to choose?

• If you only use GNOME (without Budgie) -> use indicator-sysmonitor-no-budgie-git

• If you use Budgie (whether you also use GNOME or not) -> use indicator-sysmonitor-budgie-git

Note: The "-budgie-git" version depends on "budgie-desktop", while the "-no-budgie-git" version does not.

Which package to choose?

• If you only use GNOME (without Budgie) -> use indicator-sysmonitor-no-budgie-git

• If you use Budgie (whether you also use GNOME or not) -> use indicator-sysmonitor-budgie-git

Note: The "-budgie-git" version depends on "budgie-desktop", while the "-no-budgie-git" version does not.

@homerhsing:

budgie-desktop CANNOT be listed as a required build dependency, as that would prevent users who are not running Budgie ... the upstream project does not declare "budgie-desktop" as a required dependency.

Prevent users from doing what? That's not a complete statement. It does not affect the appindicator / no-budgie package. budgie-desktop is required to build when the budgie=true Meson flag is used as you noticed. It's only a runtime dependency for the Budgie plugin. You saw that I created two separate build directories in my PKGBUILD, right? There was no reason to split out a separate package creating unecessary complication and confusion for users.

Note that makepkg does not consider split package depends when checking if dependencies are installed before package building and with --syncdeps. All packages required to make the package are required to be specified in the global depends and makedepends arrays.

-- https://man.archlinux.org/man/PKGBUILD.5#PACKAGE_SPLITTING

FYI, both packages require libayatana-appindicator. libappindicator (previously libappindicator-gtk3) is a fallback for Ubuntu.

ah i see, yeah. thanks for the additional context

Hi @coderobe, This is not "patched reuploads".

We need to support two groups of users: those using Budgie and those who are not using Budgie at all.

The previous approach was to build the upstream source twice — once requiring Budgie and once not. Even users without Budgie still had to build the upstream source in "Budgie" mode.

However, this approach no longer works properly since the upstream project migrated to Meson and explicitly checked for Budgie.

The root cause is that we can no longer build the upstream source twice - that's broken.

This is why I split the original package into two separate AUR packages. Now users only need to build the upstream source once. The users without Budgie will not have to build the upstream source requiring "Budgie".

@homerhsing that is not a great approach... please fix here instead of creating patched reuploads

Thank you @yochananmarqos.

budgie-desktop CANNOT be listed as a required build dependency, as that would prevent users who are not running Budgie.

Besides, the upstream project does not declare "budgie-desktop" as a required dependency.

Thanks for your comment and your PKGBUILD file though. But I've addressed the issue using a different approach.

@georgelpreput and others who are not using Budgie: you can install the AUR package indicator-sysmonitor-no-budgie-git. It builds successfully with Meson, works well with GNOME, not required budgie.

@homehsing: budgie-desktop is a required build dependency with the new Meson build system. Build in a build() function, not in the the package() function.

Improved PKGBUILD (paste expires in one month)

Hi @georgelpreput,
Thanks for the feedback!

For now, please continue to use the previous version (r139.a75456c-1). It should work perfectly on GNOME as before.

There is actually no functional difference between r139 and r140 except that upstream switched the build system from Make to Meson.

I'm looking into the Budgie-related confusion right now.

I'm a bit confused, have been using this package with GNOME for years now, but the last few versions seem to require Budgie? The project on GitHub mentions this should work on GNOME (and yes, I'm running now an older version of this very package on GNOME), while there's also a separate indicator-sysmonitor-budgie-git which in my understanding should be the one requiring Budgie. What am I missing here?

❯ pacman -Q | grep indicator-sysmonitor
indicator-sysmonitor-appindicator-git r139.a75456c-1

==> Making package: indicator-sysmonitor-git r140.cc5d095-2 (Thu 15 Jan 2026 02:54:36 AM CET)
==> Retrieving sources...
  -> Cloning indicator-sysmonitor git repo...
Cloning into bare repository '/home/georgelpreput/.cache/paru/clone/indicator-sysmonitor-git/indicator-sysmonitor'...
...
==> Making package: indicator-sysmonitor-git r140.cc5d095-2 (Thu 15 Jan 2026 02:54:41 AM CET)
...
==> Sources are ready.
indicator-sysmonitor-git-r140.cc5d095-2 (indicator-sysmonitor-appindicator-git): parsing pkg list...
==> Making package: indicator-sysmonitor-git r140.cc5d095-2 (Thu 15 Jan 2026 02:54:45 AM CET)
...
==> Entering fakeroot environment...
==> Starting package_indicator-sysmonitor-budgie-git()...
The Meson build system
Version: 1.10.0
Source dir: /home/georgelpreput/.cache/paru/clone/indicator-sysmonitor-git/src/indicator-sysmonitor
Build dir: /home/georgelpreput/.cache/paru/clone/indicator-sysmonitor-git/src/indicator-sysmonitor/build
Build type: native build
Project name: indicator-sysmonitor
Project version: 0.11.0
Host machine cpu family: x86_64
Host machine cpu: x86_64
Program python3 found: YES (/usr/bin/python)
WARNING: Project targets '>= 0.59' but uses feature introduced in '0.60.0': dependency with more than one name.
Found pkg-config: YES (/usr/bin/pkg-config) 2.5.1
Found CMake: /usr/bin/cmake (4.2.1)
Run-time dependency budgie-3.0 found: NO (tried pkgconfig and cmake)
Run-time dependency budgie-2.0 found: NO (tried pkgconfig and cmake)
Run-time dependency budgie-1.0 found: NO (tried pkgconfig and cmake)

../budgie/meson.build:10:13: ERROR: Dependency "budgie-1.0" not found, tried pkgconfig and cmake

A full log can be found at /home/georgelpreput/.cache/paru/clone/indicator-sysmonitor-git/src/indicator-sysmonitor/build/meson-logs/meson-log.txt
WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated.
==> ERROR: A failure occurred in package_indicator-sysmonitor-budgie-git().
    Aborting...
error: failed to build 'indicator-sysmonitor-git-r140.cc5d095-2 (indicator-sysmonitor-appindicator-git)': 

@homerhsing Thanks!