AUR (en) - lmms-git

Git Clone URL:	https://aur.archlinux.org/lmms-git.git (read-only, click to copy)
Package Base:	lmms-git
Description:	The Linux MultiMedia Studio.
Upstream URL:	https://lmms.io
Licenses:	GPL2
Conflicts:	lmms
Provides:	lmms
Submitter:	Wintervenom
Maintainer:	xente
Last Packager:	xente
Votes:	32
Popularity:	0.003342
First Submitted:	2009-04-19 19:14 (UTC)
Last Updated:	2026-05-02 21:15 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Xyne commented on 2017-10-21 12:30 (UTC)

This PKGBUILD follows the one of the non-git version in the official repos without asking too many questions for ease of maintenance. Ask the maintainer there why the build system uses multilib-gcc and wine. I am orphaning this package as I no longer use the git version. The current build fails due to a missing dependency on rpmalloc. The sources seem to be here [1]. A package will be needed. Regards, Xyne [1] https://github.com/rampantpixels/rpmalloc

milkii commented on 2017-10-18 23:27 (UTC)

i'm confused; if lmms is both 64 and 32 bit, why does this package try to go the 32bit path with gcc-multilib, etc?

Xyne commented on 2017-01-07 00:08 (UTC)

@kerbingamer376 It's a *-git package. It downloads the latest version of the master branch at build time automatically. Unless the build steps themselves have changed, it will always build the latest version.

<deleted-account> commented on 2017-01-06 17:47 (UTC)

is this updated to 1.2.0-RC2?

WhitleyStriber commented on 2016-09-26 00:04 (UTC) (edited on 2016-09-26 00:22 (UTC) by WhitleyStriber)

For HiDPI support, download the lmms-qt5-git instead.

Xyne commented on 2016-04-14 23:22 (UTC)

@Xylemon I try to follow the official package as closely as possible. The optdeps have been updated to match. It makes no sense to add ALSA or OSS to the optdeps: there is no single package for either nor a virtual "provided" package (such as e.g. java-runtime). Besides, optdeps are for packages that are not required but which extend or enhance the functionality of the package. Being able to interface with various backends to provide sound is not an extension, just a way to provide the same thing by different means. At least one sound system is expected and for an audio package sound would presumably be a dep, not an optdep ;)