Arch Linux

Hmm, OK. I did not understand how it works.
I thought it was a selection. From what you say, everyone build a different package depending on the time it installs it. I understand now.

We try to push commits thaht compiles well, but it does not guarantee that things will not be broken. There is a fact, the code is very old and rusty, and some efforts to update it transform it into an unstable alchemy difficult to stabilize. It is both the bleeding edge and both the old and rusty. ;)

So users of this package know what to expect… It is not a problem, but it means that we need another stable packages for other people.

Thanks for what you do.

Hi @illwieckz, I created a new xqf-git package here:

https://aur.archlinux.org/packages/xqf-git/

I will request this one be deleted or merged into that one.

The way VCS packages work on Arch Linux is that when the user makes this PKGBUILD, it automatically pulls the latest version from git. I can specify a branch or a specific commit, but it's standard for PKGBUILDs to just pull the latest from master. Most projects' master branch is usually in a "buildable" state and Arch Linux users know there may be some inherit instability or problems by being on the bleeding edge :) I have it setup like that right now and it's working OK, but if it becomes too unstable or not able to be built, I can force a specific version.

Hi, I created an issue dedicated to help you to package XQF 1.0.6:
https://github.com/XQF/xqf/issues/95

Hi, XQF has moved to Github: https://github.com/XQF/xqf/

An 1.0.6 release has been published, see https://github.com/XQF/xqf/releases ;-)

Beware, the repository is in active cleaning, many things can break so I heavily recommend you tu uses the releases. We will try to release early and often.

If you really want to follow the git repo, the last safe commit is https://github.com/XQF/xqf/commit/fb2ba3cd1ff6f93a022548c15e03116bd0945be7

Please do not use any newer commit without asking before. ;-)

Thanks a lot for what you do.

Thanks, I removed gdk-pixubf from the deps.

Removing gdk-pixbuf from the makedepends saved me from having to install gtk and it seems to have worked fine. Also, the fix posted by mathias.steiger for the qstat package works with the qstat-svn package. Just thought I'd let you know. Thanks You.

Thanks! I updated the PKGBUILD.

Bugfix for "error: 'pkglibdir' is not a legitimate directory for 'PROGRAMS'"

insert:
sed "s#pkglib_#pkglibexec_#g" -i src/Makefile.am
before ./automake.sh in build()

The easier (only?) way to get this (and qstat-svn) to build is to install older versions of autoconf and automake. I used downgrade (https://aur.archlinux.org/packages/downgrade/) to install autoconf 2.68-2 and automake 1.11.1-3.

Damn, after applying what smudge has said, I can't create a package, because there are some errors also in installation routine. So, i have recompiled xqf (1.05) package, but I have copied in it the xqf executable from svn version.

Now, I've an updated xqf in my system.

@smudge
It works for me.

xqf-svn doesn't build anymore.

I think autogen.sh is broken (I think because of automake & autoconf updates a while ago) because it fails to provide some Makefile.in files so I copied them across from the standard xqf 1.0.5 AUR package and to my surprise it built & worked!

I wound up doing something like:

./autogen.sh --prefix=/usr
aclocal
autoconf
automake --add-missing
./configure --enable-gtk2 --prefix=/usr LIBS='/usr/lib/libX11.so.6 /lib/libdl.so.2'
--(copy missing Makefile.in files from http://downloads.sourceforge.net/xqf/xqf-1.0.5.tar.gz)--
make

I'm sure the above is totally wrong, I don't don't understand these auto* things.

Probably best if you have a look at it :)

Thanks, I updated the PKGBUILD

Build fails for me (worked fine a few months ago) but can be fixed by changing: ./configure --enable-gtk2 --prefix=/usr
to: ./configure --enable-gtk2 --prefix=/usr LIBS='/usr/lib/libX11.so.6 /lib/libdl.so.2'