Search Criteria
Package Details: muse-git 4.0.0-1
Git Clone URL: | https://aur.archlinux.org/muse-git.git (read-only, click to copy) |
---|---|
Package Base: | muse-git |
Description: | A MIDI/Audio sequencer with recording and editing capabilities |
Upstream URL: | http://muse-sequencer.org/ |
Keywords: | alsa daw jack music |
Licenses: | |
Conflicts: | |
Provides: | |
Submitter: | milk |
Maintainer: | aquilarubra |
Last Packager: | aquilarubra |
Votes: | 3 |
Popularity: | 0.018638 |
First Submitted: | 2019-02-03 23:47 |
Last Updated: | 2020-01-19 18:58 |
Dependencies (24)
- fluidsynth (fluidsynth-git)
- gcc-libs-multilib (gcc-libs-multilib-x32, gcc-libs-multilib-git, gcc-libs-git, gcc-libs)
- gtkmm
- jack2 (jack2-git)
- lib32-gtk2 (lib32-gtk2-git, lib32-gtk2-minimal-git)
- liblo (liblo-git, liblo-ipv6)
- qt5-base (qt5-base-git, qt5-base-fractional-fix, qt5-base-headless)
- rtaudio
- cmake (cmake-git) (make)
- dssi (make)
- dssi-vst (dssi-vst-git) (make)
- gcc (gcc-multilib-x32, fastgcc, gcc-multilib-git, gcc-git) (make)
- ladish (ladish-git, ladish-no-gui) (make)
- ladspa (make)
- liblo (liblo-git, liblo-ipv6) (make)
- lv2 (lv2-git) (make)
- qt5-tools (qt5-tools-git) (make)
- dssi (optional) – dssi plugin support
- dssi-vst (dssi-vst-git) (optional) – dssi-vst plugins support
- ladish (ladish-git, ladish-no-gui) (optional) – LASH session support
- ladspa (optional) – ladspa plugin support
- lv2 (lv2-git) (optional) – lv2 plugin support
- python2 (optional) – Python scripting
- python2-pyqt5 (optional) – Python scripting
Latest Comments
1 2 3 Next › Last »
donarturo commented on 2020-06-18 20:06
At github I got an advice to disable LV2_MAKE_PATH[1]. Is necessary just change -DENABLE_LV2_MAKE_PATH=1 to -DENABLE_LV2_MAKE_PATH=0 .
[1]Github discussion
donarturo commented on 2020-06-18 14:13
While building after latest upgrade of Arch there are errors:
yochananmarqos commented on 2020-01-27 19:53
@aquilarubra: For one, v4.0.0 does not exist. You can't just invent a
pkgver
. Build the package, thepkgver
gets updated, push the changes. It's as simple as that. I'm not going to argue with you, I'm just asking you to follow package guidelinesaquilarubra commented on 2020-01-27 19:33
Yes, but it is then updated. As the pkgver variable is used below declaration, before the pkgver() function, I feel natural to leave the initialization. I didn't try to remove it - maybe I mistake, but it does no harm.
yochananmarqos commented on 2020-01-27 19:27
@aquilarubra: No, I mean the
pkgver
in the PKGBUILD here is still 4.0.0.aquilarubra commented on 2020-01-27 18:53
Strange, when I compiled, I got a file with the correct version, 3.1... etc.
yochananmarqos commented on 2020-01-27 18:11
@aquilarubra: When
makepkg
is run, thepkgver()
array will automatically update thepkgver
. That was not done here, the fictitious 4.0.0 is still in use.aquilarubra commented on 2020-01-27 17:44
I built it and it works. Closed
yochananmarqos commented on 2020-01-20 01:11
@aquilarubra: Not quite. You missed something, see my previous comment. Please actually use
makepkg
to build this before pushing updates.yochananmarqos commented on 2020-01-12 23:20
Packages provide themselves, this should only provide and conflict with
muse
.Don't rename the source to
muse-git
.Please use a
pkgver()
function per VCS package guidelines: