Delta: Arch Linux support

Created on 7 Feb 2020  路  13Comments  路  Source: dandavison/delta

Please be careful when you re-release a version like 0.0.16 because some package systems use sha256sum to build the package for the Linux distro, so the re-release needs an upgrade in https://aur.archlinux.org/packages/git-delta

Maybe some other issues could happen when you do that.

The Linux kernel had an issue with the release 5.3.2 in October and they released the 5.3.3 with just 1 new commit making apologies about the noise: https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.3

Thanks 馃檪

All 13 comments

Ah, of course, that was stupid of me. Thanks for the reminder, I won't do it again.

Is the archlinux package in a correct state now?

Yep, @Kr1ss-XD has upgraded the package.

Thx a lot for providing us your project, and releasing under a free license btw. I do use this software myself. :+1:

@Kr1ss-XD is it still necessary to include clang and llvm as dependency for installing this package ?

Maybe we use build release strategy used by other tools like [bat] or [ripgrep].

As for a pre-built package, this would have to be git-delta-bin (btw I think there actually _is_ such a package in the AUR, iirc).
Otherwise, non '-bin' packages are built locally. I can't build git-delta in a clean chroot w/o clang and llvm. So yes, those are needed as build time dependencies.
makepkg will uninstall them after building the package if called w/ the -r flag.

E/ The bat PKGBUILD from the Archlinux [community] repo also depends on clang :wink:

Yes got it. Thanks

Does the ArchLinux installer rely on any of the .tar.gz archive files that are hosted on the GitHub releases page? I was contemplating just hosting the executable directly, rather than wrapping it up in a compressed archive (since the compressed archive only serves to make it slightly more inconvenient for human users who want to download the executable).

@dandavison no, the bin package use the .deb version.
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=git-delta-bin

Thanks @navarroaxel.

Well there are basically two ways of packaging for the AUR. Default way is to have the package built locally in the users side. In the other hand, there may be a ...-bin package with distributes the binary directly.
In case of git-delta, there is a binary package as well as one to be built locally from source to be chosen from.

E/ git-delta pulls the source tarball, so it would be nice if you could keep it in the releases tree, if it's not creating any inconveniences for you.

@Kr1ss-XD thanks, I'll keep the tarball in the releases tree. I'll mention it here again if I start also hosting the binaries directly in the releases tree.

Great, thank you !

Was this page helpful?
0 / 5 - 0 ratings