Package Details: renoise 3.4.4-1

Git Clone URL: https://aur.archlinux.org/renoise.git (read-only, click to copy)
Package Base: renoise
Description: A music composition program
Upstream URL: https://www.renoise.com
Keywords: daw music renoise tracker
Licenses: custom:renoise
Conflicts: renoise3-demo
Provides: dssi-host, ladspa-host, vst-host, vst3-host
Submitter: niv
Maintainer: dsonck92
Last Packager: dsonck92
Votes: 22
Popularity: 0.016250
First Submitted: 2016-01-28 01:16 (UTC)
Last Updated: 2024-07-27 23:02 (UTC)

Dependencies (4)

Required by (78)

Sources (3)

Pinned Comments

NeoZelox commented on 2016-09-13 04:22 (UTC)

for any fellow noobs out there, you have to buy/download the official tar file from renoise.com, put it in the same directory as PKGBUILD, and ~then~ make the package

Latest Comments

1 2 3 Next › Last »

tkna commented on 2024-09-08 14:42 (UTC) (edited on 2024-09-08 14:43 (UTC) by tkna)

I apologize if I am wrong, but I checked the permissions on the files deployed with such a command and found that most of them were granted execute permission. https://0x0.st/XwR9.txt

pacman -Ql renoise | cut -d ' ' -f 2- | LANG=C xargs -I{} ls -ld "{}" > renoise-list.txt

I think it would be better to reflect the process described in install.sh , but what do you think?

mutt commented on 2024-07-26 01:35 (UTC)

consider adding provides=("vst-host" "vst3-host" "ladspa-host" "dssi-host") to the PKGBUILD

tkna commented on 2023-09-19 02:45 (UTC)

please update: pkgver = 3.4.3

NN777 commented on 2022-06-16 01:03 (UTC)

please update: pkgver = 3.4.2

SunRed commented on 2022-04-16 13:50 (UTC) (edited on 2022-04-16 14:00 (UTC) by SunRed)

Since renoise 3.4 introduced builds for ARM, would it be possible to add ARM support to the package? A possible PKGBUILD file could look like this:

pkgname='renoise'
pkgver='3.4.1'
pkgrel='1'
pkgdesc='A music composition program'
arch=('x86_64' 'aarch64' 'armv7h')
url='https://www.renoise.com'
license=('custom:renoise')
depends=('alsa-lib' 'libx11' 'gcc-libs')
optdepends=('jack: For JACK audio support')
options=('!strip')
conflicts=('renoise3-demo')

source_x86_64=("file://rns_${pkgver//./}_linux_x86_64.tar.gz")
source_aarch64=("file://rns_${pkgver//./}_linux_arm64.tar.gz")
source_armv7h=("file://rns_${pkgver//./}_linux_armhf.tar.gz")

sha256sums_x86_64=('SKIP')
sha256sums_aarch64=('SKIP')
sha256sums_armv7h=('SKIP')

_arch='x86_64'

case "$CARCH" in
 'aarch64') _arch='arm64' ;;
 'armv7h')  _arch='armhf' ;;
esac

package() {
    cd "$srcdir/rns_${pkgver//./}_linux_${_arch}"

    mkdir -p "$pkgdir/usr/share/renoise-$pkgver"
    cp -r Resources/* "$pkgdir/usr/share/renoise-$pkgver"

    install -Dm 755 'renoise' "$pkgdir/usr/bin/renoise"
    install -Dm 644 'Installer/renoise.desktop' "$pkgdir/usr/share/applications/renoise.desktop"
    install -Dm 644 'Installer/renoise.1.gz' "$pkgdir/usr/share/man/man1/renoise.1.gz"
    install -Dm 644 'Installer/renoise-pattern-effects.5.gz' "$pkgdir/usr/share/man/man5/renoise-pattern-effects.5.gz"
    install -Dm 644 'License.txt' "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
    install -Dm 644 'Installer/renoise.xml' "$pkgdir/usr/share/mime/packages/renoise.xml"
    install -Dm 644 'Installer/renoise-48.png' "$pkgdir/usr/share/icons/hicolor/48x48/apps/renoise.png"
    install -Dm 644 'Installer/renoise-64.png' "$pkgdir/usr/share/icons/hicolor/64x64/apps/renoise.png"
    install -Dm 644 'Installer/renoise-128.png' "$pkgdir/usr/share/icons/hicolor/128x128/apps/renoise.png"
}

Since renaming the source tar via source=("myfile.tar.gz"::"file://myfile-x86_64.tar.gz") apparently does not work (not sure if it's a makepkg bug) for local files via file:// I added this workaround by mapping $CARCH to the correct string used by renoise so that cd'ing into the right directory is possible. Also note that the prepare() function is not necessary anymore.

B00daW commented on 2021-05-18 22:39 (UTC)

please update to v3.3.2. thanks!

AYANE-69 commented on 2020-09-07 16:41 (UTC)

@dvzrv @spider-mario Whatever works and is most inline with the arch-correct way of doing things is fine by me. Based on what you said the PKGBUILD could simply be modified to look like this pastebin and we would be set.

dvzrv commented on 2020-09-07 09:46 (UTC)

@DYSEQTA: Your statements about the install file are wrong though.

Pacman takes care of things like these using hooks (and has been for some years now). All that is necessary is to install icons to the correct location and depend on hicolor-icon-theme. No install script required.

spider-mario commented on 2020-09-07 09:20 (UTC) (edited on 2020-09-07 09:21 (UTC) by spider-mario)

Why not just create the appropriate files in $pkgdir/usr/share/icons and thus have them owned by the package, instead of relying on a runtime script that will leave stuff behind if it has a typo?