Package Details: qtile-git 0.29.0.r55.gfd6b2cd-1

Git Clone URL: https://aur.archlinux.org/qtile-git.git (read-only, click to copy)
Package Base: qtile-git
Description: A full-featured, pure-Python tiling window manager
Upstream URL: https://github.com/qtile/qtile
Licenses: MIT
Conflicts: qtile
Provides: qtile
Submitter: Mr.Elendig
Maintainer: xiota (elParaguayo)
Last Packager: elParaguayo
Votes: 69
Popularity: 0.31
First Submitted: 2008-09-23 19:38 (UTC)
Last Updated: 2024-12-19 07:07 (UTC)

Pinned Comments

xiota commented on 2024-09-20 20:36 (UTC) (edited on 2024-09-20 20:49 (UTC) by xiota)

Re: The tests take a very long time to run.

When I adopted this package, checks were disabled. Upon enabling them, I saw a large number of failures. Leaving the checks enabled will prevent problems from going unnoticed.

Users who rebuild frequently may not need to run checks after every build. They may opt for one of the following:

  • Pass the --nocheck option to makepkg to skip the tests.
  • Configure makepkg to disable checks by default.
    • Edit the BUILDENV array in /etc/makepkg.conf.
    • Occasionally use the --check option.

Latest Comments

1 2 3 4 5 6 .. 11 Next › Last »

elParaguayo commented on 2024-12-18 11:03 (UTC)

xiota - do you want me to take over ownership of this? I'm one of the qtile developers and also maintain the qtile-extras AUR packages.

xiota commented on 2024-09-20 20:36 (UTC) (edited on 2024-09-20 20:49 (UTC) by xiota)

Re: The tests take a very long time to run.

When I adopted this package, checks were disabled. Upon enabling them, I saw a large number of failures. Leaving the checks enabled will prevent problems from going unnoticed.

Users who rebuild frequently may not need to run checks after every build. They may opt for one of the following:

  • Pass the --nocheck option to makepkg to skip the tests.
  • Configure makepkg to disable checks by default.
    • Edit the BUILDENV array in /etc/makepkg.conf.
    • Occasionally use the --check option.

xiota commented on 2024-09-20 20:31 (UTC) (edited on 2024-09-20 20:50 (UTC) by xiota)

Aren't the tests run before merging to main?

While qtile may have a policy to never commit with failed pre-checks, not all projects do. Some projects don't always follow their own policies. Mistakes can happen.

So the repository could never be in a state where the tests would have failed.

There is at least one failed checkin shown in the commit history (currently on second page).

What's the point then in testing again on each install?

Even if upstream checks never failed, the local build environment may be different. Your config may be different from mine or any other users. So local checks could still fail.

bibermann commented on 2024-09-20 17:17 (UTC)

@xiota Aren't the tests run before merging to main? So the repository could never be in a state where the tests would have failed. What's the point then in testing again on each install? Just curious ;)

zordsdavini commented on 2024-08-27 05:39 (UTC)

@xiota thank you for taking care for the package. I didn't know about makepkg --nocheck - that changes everything, so no need to make installation difficult

xiota commented on 2024-08-27 05:07 (UTC) (edited on 2024-08-27 05:28 (UTC) by xiota)

@zordsdavini The tests do take a long time to run, but are useful to make sure the package has the best chance of working. You can skip them with makepkg --nocheck.

I do have scripts that check workflow results, but PKGBUILDs should run without requiring any user input because they may be run on headless servers. So I don't know how they could be integrated into packages.

GitHub also sometimes reports different results for the same commit on different pages.

zordsdavini commented on 2024-08-27 04:43 (UTC)

Is it tests are really needed to be run on install? It takes ages. Maybe we could take status from https://github.com/qtile/qtile/actions/workflows/ci.yml and do something on that, ex., output the result and if it doesn't pass - ask "Do you want to continue?"

santzes commented on 2024-07-14 14:36 (UTC) (edited on 2024-07-14 14:37 (UTC) by santzes)

After wlroots got updated to 0.18, I needed to add these lines to build() to use the older wlroots instead

export PKG_CONFIG_PATH="/usr/lib/wlroots0.17/pkgconfig:$PKG_CONFIG_PATH"
export CFLAGS="$CFLAGS $(pkg-config --cflags wlroots)"
export LDFLAGS="$LDFLAGS $(pkg-config --libs wlroots)"

This would probably work as well:

export CFLAGS="$CFLAGS -I/usr/include/wlroots0.17"
export LDFLAGS="$LDFLAGS -L/usr/lib/wlroots0.17"

Got missing headers with wlroots 0.18 so couldn't get it to compile.

mo3r commented on 2023-12-13 05:18 (UTC) (edited on 2023-12-13 05:24 (UTC) by mo3r)

For successful build you need to add CFLAGS and LDFLAGS export, as it was in previous versions of PKGBUILD, but for version wlroots 0.16 instead of 0.15

diff --git a/PKGBUILD b/PKGBUILD
index 4d7655a..2802b3e 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -4,7 +4,7 @@
# This PKGBUILD packages Qtile with X11 dependencies.

pkgname=qtile-git
-pkgver=0.22.1.r215.g142dc80a
+pkgver=0.23.0.r86.ge0b6b0e2
pkgrel=1
pkgdesc="A full-featured, pure-Python tiling window manager - X11. (git version)"
arch=('x86_64')
@@ -78,6 +78,8 @@ pkgver() {

build() {
 cd qtile
 +  export CFLAGS="$CFLAGS -I/usr/include/wlroots0.16"
 +  export LDFLAGS="$LDFLAGS -L/usr/lib/wlroots0.16"
 python -m build --no-isolation --wheel
 ./scripts/ffibuild
}

1 2 3 4 5 6 .. 11 Next › Last »