Package Details: lightworks-beta 2023.2-1

Git Clone URL: (read-only, click to copy)
Package Base: lightworks-beta
Description: Lightworks Beta is the public Beta branch for Lightworks, the professional video editing suite, updated weekly
Upstream URL:
Licenses: custom
Conflicts: lightworks, lwks-beta
Provides: lightworks
Replaces: lwks-beta
Submitter: jamnor
Maintainer: jamnor
Last Packager: jamnor
Votes: 16
Popularity: 0.059232
First Submitted: 2023-10-14 04:30 (UTC)
Last Updated: 2023-10-15 05:58 (UTC)

Latest Comments

1 2 3 4 Next › Last »

jamnor commented on 2023-10-17 01:41 (UTC)

That's good to know, but the AUR submission guidelines don't actually say any of this about replaces:

This is what it actually says:

Do not use replaces in an AUR PKGBUILD unless the package is to be renamed, for example when Ethereal became Wireshark. If the package is an alternate version of an already existing package, use conflicts (and provides if that package is required by others). The main difference is: after syncing (-Sy) pacman immediately wants to replace an installed, 'offending' package upon encountering a package with the matching replaces anywhere in its repositories; conflicts, on the other hand, is only evaluated when actually installing the package, which is usually the desired behavior because it is less invasive.

It actually suggests that replaces is what you want in this particular scenario, where we want people to immediately uninstall lwks-beta and install lightworks-beta when syncing. We want the more invasive behavior. The discussion on pacman does not seem very useful as it is not used to install AUR packages; AUR helpers are. There are also no AUR repositories to sync, so the pacman -Sy reference is interesting, but not useful to know with regard to the AUR.

I would edit the wiki page to align with what you've written here (it's very valuable to know!), but I don't understand it well enough. Is this something you could do?

MarsSeed commented on 2023-10-16 22:25 (UTC)

And actually 'replaces' field is not served by AURweb RPC webcall interface, therefore AUR helpers ignore that field.

MarsSeed commented on 2023-10-16 22:24 (UTC)

No, replaces is not proper to use instead of conflicts, and AUR submission guidelines say that 'replaces' should generally be avoided on AURweb.

jamnor commented on 2023-10-15 06:01 (UTC)

I just updated to the Oct 12, 2023 build.

We're now using the link to the .deb package instead of the older S3 link. This aligns with the lightworks package, and also simplifies maintenance because we don't need to bump as many variables. Also, if LWKS ever changes their CDN backend, the link will probably still work.

jamnor commented on 2023-10-14 08:25 (UTC)

My understanding is that the replaces array is enough according to the documentation:

But I'll add conflicts just in case.

I wasn't sure about the provides array, but adding it seems to be the right thing to do, so I've done that now. I was a bit confused as the lightworks package had lightworks in the provides array. I'm not sure what the effect is supposed to be based on the wiki, as I thought conflicts would force people to uninstall lightworks to install lightworks-beta.

MarsSeed commented on 2023-10-14 07:13 (UTC)

Also please add conflicts=(lwks-beta), otherwise people who had that one installed previously and now try to migrate to this newly renamed package might face problems.

MarsSeed commented on 2023-10-14 07:08 (UTC)

Thanks for the rename. Please kindly also add provides=(lightworks).

jamnor commented on 2023-10-14 04:39 (UTC)

I've created a replacement package at lightworks-beta and submitted a merge request against lwks-beta to merge into lightworks-beta. Thanks for pointing this out, MarsSeed!

MarsSeed commented on 2023-10-12 07:41 (UTC)

Please kindly rename this to lightworks-beta, to align with AUR/lightworks, and to upstream's release archive name.

jamnor commented on 2023-08-31 13:20 (UTC) (edited on 2023-08-31 14:42 (UTC) by jamnor)

Here's a PKGBUILD for August 23rd, 2023 build of Lightworks beta. You'll need to agree to be a beta tester and download the .deb package to the same folder as the PKGBUILD. Then run makepkg -si. LWKS recommends backing up your project data, which is super quick and easy:

Just bump the lwksver, sha512sums, and lwksbuild for newer builds.

# Maintainer: Marcin Nowak <marcin [dot] j [dot] nowak [at] gmail [dot] com>
# Contributor: Mateus Rodrigues Costa <charles [dot] costar [at] gmail [dot] com>
# Contributor: PieterDeBruijn <arch [at] pieterdebruijn [dot] nl [dot] com>
# Contributor: stjhimy <stjhimy [at] gmail [dot] com>
# Contributor: CYB3R <dima [at] golovin [dot] in>
# Contributor: Sarkasper <kasper [dot] menten [at] gmx [dot] com>
# Contributor: Scias <shining [dot] scias [at] gmail [dot] com>
# Contributor: darzki <darzki [at] o2 [dot] pl>
# Contributor: N30N <archlinux [at] alunamation [dot] com>
# Contributor: anthrit <anthrit [at] anthware [dot] com>
# Contributor: jamnor <software [at] vncompat [dot] org>

pkgdesc="Lightworks Beta is the public Beta branch for Lightworks, the professional video editing suite"
depends=('cairo' 'gdk-pixbuf2' 'glib2' 'libjpeg-turbo' 'pango' 'curl' 'gtk3' 'portaudio' 'openssl' 'libgl' 'libtiff' 'libutil-linux' 'ffmpeg' 'glu' 'libedit' 'nvidia-cg-toolkit')
optdepends=('nvidia-utils: only for nVidia users' 'libc++: only for BlackMagic RAW support (BRAW)' 'libc++abi: only for BlackMagic RAW support (BRAW)')


package() {
    msg2 "Extracting data.tar.xz"
    bsdtar -zxf data.tar.xz -C "$pkgdir"

    msg2 "Moving udev folder from /lib to /usr/lib"
    mv "$pkgdir"/lib/udev "$pkgdir"/usr/lib
    rmdir "$pkgdir"/lib

    msg2 "Copying copyright file and creating a license dir"
    install -Dm644 "$pkgdir"/usr/share/doc/lightworks/copyright \
    ln -sr "$pkgdir"/usr/share/licenses/lightworks "$pkgdir"/usr/share/licenses/$pkgname

    msg2 "Changing some needed permissions"
    chmod a+rw "$pkgdir"/usr/share/lightworks/Preferences
    chmod a+rw "$pkgdir"/usr/share/lightworks/"Audio Mixes"

I have another version of this PKGBUILD with a direct link that also works, not requiring you to manually download anything, which is what the latest PKGBUILD in this repository is using, but I'm leaving this one here as it's minimally useful in case the link/process changes.