You are not logged in.
Hi,
I noticed that the Mocha Pro software by BorixFX is not present in the AUR,
have so created a working PKGBUILD for my own use.
Since this package might interest also to others, I tried to create
an AUR compatible one, but it is my 1st one, I might have made mistakes.
Could you please review if I might publish it, or if I made mistakes and
should avoid publishing it? (at its current state, at least)
here the PKGBUILD:
# Maintainer: Francesco Yoshi Gobbo <yoshi @ fgobbo-dot-com>
pkgname="mocha-pro"
pkgver=12.0.1
pkgrel=1
pkgdesc="Award-winning Tracking and Masking by BorisFX"
arch=("x86_64")
url="https://borisfx.com/products/mocha-pro"
license=('Commercial')
depends=('glu' 'glibc' 'libglvnd' 'gcc-libs' 'xz' 'libwebp' 'openjpeg2' 'util-linux-libs' 'libx11' 'pcre2' 'zstd' 'libsm' 'libice' 'libxext' 'libxcb' 'libidn2' 'libxau' 'libxdmcp' 'libunistring' 'libxcrypt-compat')
install=mocha-pro.install
# download section, info can be found via https://vfx.borisfx.com/mocha-installer
_product=MochaPro2025
_siteurl='https://cdn.borisfx.com/borisfx/store/mochapro'
_release=46
_refid='g8b4c8cfd3c12.vfx2023'
source=("$_siteurl/$_product-$pkgver-$_release.$_refid.$arch.rpm")
# checksum not provided
sha256sums=('SKIP')
package() {
# Copy all directories from $srcdir into $pkgdir without copying the package's symlink.
find $srcdir/ -mindepth 1 -maxdepth 1 -type d | xargs cp -r -t "$pkgdir"
}
and here the mocha-pro.install
## create the directory to where the license will be installed
post_install() {
mkdir -p /usr/genarts
echo "the RLM license will be installed at /usr/genarts, you can gain temporary rw access by using chown user:user to the directory before opening the software, remember to change it back to root:root after you completed the license installation."
}
post_remove() {
echo "remember to backup your RLM license, it is located at /usr/genarts"
}
Thanks!
Last edited by FraYoshi (2025-01-22 22:02:21)
https://keybase.io/frayoshi
Pgp: B41370007e0dfc34942cfa033fc5f028e7aff594
Offline
Just noticed that I did not go through the `ldd mochapro2025` (executable) process... adding the dependencies now! Gonna update the PKGBUILD ASAP
https://keybase.io/frayoshi
Pgp: B41370007e0dfc34942cfa033fc5f028e7aff594
Offline
Okay, went through `ldd mochapro2025` and `ldd bfx-license-tool` , so have done `pacman -F <lib>` on the results, and have added this to the PKGBUILD
depends=('glu' 'glibc' 'libglvnd' 'gcc-libs' 'xz' 'libwebp' 'openjpeg2' 'util-linux-libs' 'libx11' 'pcre2' 'zstd' 'libsm' 'libice' 'libxext' 'libxcb' 'libidn2' 'libxau' 'libxdmcp' 'libunistring' 'libxcrypt-compat')
Last edited by FraYoshi (2025-01-22 22:03:25)
https://keybase.io/frayoshi
Pgp: B41370007e0dfc34942cfa033fc5f028e7aff594
Offline
That is not a valid SPDX license identifier.
ldd is recursive, don't use it for things like this.
Don't skip the checksum
Don't forget to quote all instances of variable that could have spaces, like $srcdir
Don't create untracked dirs in /usr. Create that in the package function.
Offline
Thanks Scimmia!
Gonna hunt for the license name, at the moment cannot find it, must be somewhere...
About ldd, any suggestion as alternative? Have no access to the source code..
For the checksum, I'm so going to download the package first, calculate and only then update the PKGBUILD
Thanks for the quoting tip!
The untracked file in /usr is where the software expects the node locked license to be installed, not sure how to redirect it...
Don't feel obliged to answer, and thanks for the help so far!
Last edited by FraYoshi (2025-01-23 00:41:46)
https://keybase.io/frayoshi
Pgp: B41370007e0dfc34942cfa033fc5f028e7aff594
Offline
Just create the folder in package() and add a post_install message that the license must be placed there.
See https://wiki.archlinux.org/title/PKGBUILD#install
lddtree from pax-utils is more useful to check dependencies .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline