Package Details: monique-monosynth-git r586.bf416cc2-9

Git Clone URL: https://aur.archlinux.org/monique-monosynth-git.git (read-only, click to copy)
Package Base: monique-monosynth-git
Description: Monique is a monophonic synth from Thomas Arndt
Upstream URL: https://github.com/surge-synthesizer/monique-monosynth
Licenses: GPL3, MIT
Conflicts: monique-monosynth
Provides: monique-monosynth
Submitter: apoorv569
Maintainer: apoorv569
Last Packager: apoorv569
Votes: 1
Popularity: 0.000000
First Submitted: 2021-12-31 11:20 (UTC)
Last Updated: 2024-02-26 04:40 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

silverhikari commented on 2022-06-09 23:00 (UTC) (edited on 2022-07-14 05:26 (UTC) by silverhikari)

can you set juce to pull from the develop branch and set "git -C libs/clap-juce-extensions checkout next" in prepare, as it seems without doing so the build errors out

EDIT: seems the claps-juce-extensions was fixed so that was no longer needed, and instead of the development branch it could now be 7.0.0 or newer as those version includes the need fix

slack_twot commented on 2022-02-28 00:03 (UTC)

It would be nice to see this in the main repo's, the Juce dependency adds significantly to build times ;)

apoorv569 commented on 2022-01-09 15:05 (UTC)

@silverhikari Alright I have pushed another commit, the upgrade problem should be fixed now. Please let me know if not.

silverhikari commented on 2022-01-08 23:43 (UTC) (edited on 2022-01-08 23:46 (UTC) by silverhikari)

@apoorv569 no only when you do it the first time because at the moment because of the current format it will say there is a new update even though there is none. because if you only makepkg it even though the package would then say "rxxx.xxxx" the package manager would thing it is a lower version then the current version which is "1-5" so it would not update the pkg build.

apoorv569 commented on 2022-01-07 14:07 (UTC)

@silverhikari So I should use makepkg and let the pkgver() change the pkgver variable and leave the pkgrel to 1 and increment epoch variable by 1 every time there is a new release?

The ArchWiki suggest to only use epoch when really needed.

silverhikari commented on 2022-01-07 13:16 (UTC)

hey, there is a problem with the package, as the version format that is used by pkgver and the pkver that is used by aur. for example the current version is "r527.53ebe655" while the version the package uses is "1-5" so even if there is no updates for the git, the package manager will always say there is a new version released. to fix this you would have to update the package version using makepkg then add a 1 to the eoch so it will confirm that this is the new format.

apoorv569 commented on 2022-01-06 08:53 (UTC)

@aakarpov Okay, so I fixed one of the suggestion you gave me, I removed sudo from the package(). Now for CMake, I don't have experience with that build system. If someone has a solution please share.

aakarpov commented on 2022-01-03 09:32 (UTC) (edited on 2022-01-03 09:33 (UTC) by aakarpov)

@apoorv569 1. There is no need of sudo in package() section of PKGBUILD. It's packaging, not installing (right now You can not get anything from "pacman -Ql" and (surprise!) can't remove it, /usr/bin/MoniqueMonosynth persists after deletion of package). You can paint me pink, but it's a bug. And similar sodomy happens in Your second package, if I misunderstand it wrong. 2. Even if upstream insists on static build, there must be the way to avoid it. At the moment I didn't dive deep enough into (just clone git, checkout JUCE and cmake), so second suggestion is just a suggestion and probably there will be more.

apoorv569 commented on 2022-01-03 07:44 (UTC)

@aakarpov Please share your thoughts and suggestions or any other advice.

1 2 Next › Last »