Arch Linux User Repository

For those looking for something more stable than the alpha/default branch, there's another git pkgbuild for the 2.3 branch (beta), which should be reliable enough for daily use: https://aur.archlinux.org/packages/mixxx_beta-git/

This package will automatically retrieve and build the latest development snapshot of Mixxx from git (default branch).

It does not need to be updated on every release, so please do not flag out of date unless the build breaks or any actual packaging issue.

@rryan: You're absolutely right, the branch + revision number should match what we get in the About dialog (it used to work properly in the 1.12 days, but I have to admit I didn't spend too much time on it since then, and am not too fresh on the topic).

Anyway, thanks for the pointers. The revision works, but I still can't get the branch right, I always seem to end up with the latest stable tag at best. Your python build script is using "git rev-parse --abbrev-ref HEAD", which wouldn't work unless I checkout again the specific branch in the pkgversion function, so there's maybe something I can do here (or that I should have done).

I'll continue working on it

Looking at https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

I think for "RELEASE.rREVISION" "$(git branch | grep * | cut -d ' ' -f2).r$(git log --pretty=oneline --first-parent | wc -l)" might make sense. WDYT?

@gimmeapill, thanks for this!

RE: pkgver. I'm definitely new to Arch packaging.

If you'd like to use the Mixxx convention for referring to builds, we use:

"branch-name rXXXX" to refer to a build, (you see this string in the Help -> About box, and we ask users for the info when they report bugs).

Where XXXX is the commit "number", computed with

$ git log --pretty=oneline --first-parent | wc -l

the Python version Mixxx's build system uses is here: https://github.com/mixxxdj/mixxx/blob/1c7785847bd7d89866ddc5cc4e759639331f91d3/build/util.py#L73-L74

I think that might be simple and safe enough to incorporate into the pkgver function, since it already uses "git describe"?

For those looking for something more stable than the alpha/default branch, there's another git pkgbuild for the 2.3 branch (beta), which should be reliable enough for daily use: https://aur.archlinux.org/packages/mixxx_beta-git/

@Kunda: This is a git package, the version is updated when you build it. Also, as per the comments below from rryan, this will fetch the current master branch = alpha, not the latest stable.

please rename the package to mixxx-git release.2.1.5.etc....

@kazakore: The pkgbuild version is updated during the build by the pkgver() function, as per the AUR git packaging guidelines: https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git

I don't really see how an AUR helper could fetch the latest git revision without going through at least the first steps of the build and executing that pkgver() function.

Even assuming that it would be doing so - for every package name that matches your wildcard without asking, this would very likely be a big red flag security wise (also it would probably not be very fast).

So what you see in the list is just the git revision as of the latest pkgbuild update - which is the correct behavior, but may be confusing if you are not familiar with AUR VCS pkgbuilds.

If you really need that feature, you could try raising it to that AUR Helper developers, but this is not something I can help with in the pkgbuild.

As for allowing side by side installation with the stable version, this is also not something that I've considered or that has been requested until now, but that could make sense. Just this is usually done by building locally (either under /local or from your home folder) & you don't want or need a package for that.

If there is some popular demand, I can try to have a look, but then better do things properly and duplicate also the user settings and library db under /home - this will probably be less trivial...unless there is a Mixxx supported way?

Please correct this so it either shows a version relevant to what is actually going to be installed, instead of showing the completely wrong version which can be installed via the Community repo.

$ yay mixxx
3 aur/mixxx-qt5 2.1.4-1 (+2 0.96%) 
    free, open source software for digital DJ'ing, Qt5 version
2 aur/mixxx-git release.2.1.4.r495.gbc69f995ae-1 (+17 0.72%) (Installed: release.2.1.4.r704.g9c12473b8e-1)
    Digital DJ mixing software. Development branch from git.
1 community/mixxx 2.1.4-1 (13.5 MiB 44.1 MiB) 
    Free, open source software for digital DJ'ing.

Just saying either Git Master instead of any version number would be good enough. Or updating so it would currently save 2.3.x or 2.3-pre-alpha could work but would require occasional intervention to update by you.

Also please make it so that it does not have the same installed package name as the Community version so both can be installed at the same time. This is the usual way to do it, where git versions use package name suffix of -git so both can be installed at once if desired. It's often good to be able to have both the current stable and the development branches installed, especially of software you may rely on heavily (especially if performing in front of people using it!!)

Thanks for all the updates! We have switched to qt5 fully now (2.2 will be the first release with it).

lame is now a required dependency on the master branch.

BTW the master branch corresponds to 2.3.0 alpha. The 2.2 branch corresponds to 2.2.0 beta (not yet released), and the 2.1 branch is the current stable series (2.1.4).