Package Details: lmms-git 1.2.0.r3.g3ada5b8a1-1

Git Clone URL: (read-only)
Package Base: lmms-git
Description: The Linux MultiMedia Studio.
Upstream URL:
Licenses: GPL2
Conflicts: lmms
Provides: lmms
Submitter: Wintervenom
Maintainer: MrSoup678
Last Packager: MrSoup678
Votes: 27
Popularity: 0.000032
First Submitted: 2009-04-19 19:14
Last Updated: 2019-06-18 15:48

Latest Comments

1 2 3 4 5 Next › Last »

MrSoup678 commented on 2019-06-18 15:51

Old PKGBUILD had a bug where bash auto-completion script would install in $PKGDIR$PKGDIR (effectively). I just fixed that problem

difarem commented on 2018-11-14 17:24

Disowning, since I don't have the time to actively maintain this package.

dvzrv commented on 2018-10-18 08:34

Please switch this to qt5, so the other package can be deleted. There is no use in using qt4 anymore and keeping this duplication alive.

haawda commented on 2017-12-06 19:58

There is already a package lmms-qt5-git in AUR.

agapito commented on 2017-11-25 16:42

Should be better start using qt5 version:

build() {
cd -- "$srcdir/$_pkgname"
make -j$(nproc)

difarem commented on 2017-11-25 16:15

Adopted the package, set up git submodules so rpmalloc is built.

EDIT: well, it seems like something's wrong with the packaging. Will look into and try to fix at soon as possible.

Xyne commented on 2017-10-21 12:30

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.



milk commented on 2017-10-18 23:27

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

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.

Anonymous comment on 2017-01-06 17:47

is this updated to 1.2.0-RC2?