Arch Linux User Repository

TL;DR

please, do not blindly mark this package out-of-date, thanks =)

TS;RE

current native_messenger version is tracked using https://raw.githubusercontent.com/tridactyl/tridactyl/<put current stable version of tridactyl here>/native/current_native_version.

at the time of writing this message tridactyl is at version 1.23.0, so native_messaging's version is:

❯ curl -sL 'https://raw.githubusercontent.com/tridactyl/tridactyl/1.23.0/native/current_native_version'
0.3.6

... 0.3.6 even if there is new 0.3.7 version on GitHub Releases page.

thank you =)

@t-8ch, @alerque, thanks. now this package builds from sources using nimble. also created new firefox-tridactyl-native-bin package to provide binary version

@t-8ch, thanks a lot for detailed explanation.

• removed glibc from depends (checked the dependencies of base package =))
• removed conflicts/provides (after reading wiki again, now i see)
• for now, added only x86_64 arch. if someone can test if it builds on i686 and/or arm, let me know

@liljaylj glibc is part of the base group and all packages can rely on it to be present. The package does not conflict/provde with the -bin variant but with itself. "any" means that the package does not contain architecture specific files (only scripts, docs, data files, etc). If you want to express that the package can be built for many target architectures you should list all those architectures in the arch array. Currently only x86_64 is supported in normal ArchLinux. i686 is used by the Arch 32bit project and ArchLinux for ARM has also some tags defined.

@t-8ch

• glibc is a runtime dependency (as namcap states). i prefer to explicitly define it, as packages from official repos do
• why not? this package now conflicts with firefox-tridactyl-native-bin
• this package does not contain binaries. $arch is any because nimble should build package to target platform it runs on (not tested though)
• done. thanks

@liljaylj, thanks!

FYI a few more notes on the PKGBUILD: * There should be no need to depend on glibc * The conflicts/provides entries are not needed * This $arch should be x86_64 as the package contains binaries * The source filename should contain the package name: source=("$pkgname-$pkgver.tar.gz::https://github.com...

(The namcap tool can check both the PKGBUILD and the built package for some of these)

@t-8ch, @alerque, thanks. now this package builds from sources using nimble. also created new firefox-tridactyl-native-bin package to provide binary version

Yes, this package should --and indeed according to AUR packaging guidelines must-- be built from source and an upstream built binary edition as this currently is can be made available in a -bin package.

Would it not be better for the package to build the native client from source instead of downloading the binaries? The toolchain is available in the repositories.

Also packages built from binary normally have a -bin suffix.

@bovine3dom Good solution, thanks.

Will wait to stable version of Tridactyl to release which would include current_native_version file

Just a heads up that the native messenger is changing with the next release of Tridactyl - it's now written in Nim and lives on a different repository: https://github.com/tridactyl/native_messenger

It'll therefore be a bit harder to work out which version of the native messenger works with the current stable version of Tridactyl.

Our solution is to put the corresponding native tag in the main Tridactyl repository - https://raw.githubusercontent.com/tridactyl/tridactyl/master/native/current_native_version

You might want to look at our install script for inspiration - it takes a Tridactyl release tag and installs the corresponding native messenger for that version - https://github.com/tridactyl/native_messenger/blob/master/installers/install.sh

I expect I'll release a stable version of Tridactyl that supports the new messenger within a few weeks.