Package Details: trust-dns-git 0.23.0.alpha.5.r0.ae1428c2-1

Git Clone URL: https://aur.archlinux.org/trust-dns-git.git (read-only, click to copy)
Package Base: trust-dns-git
Description: Safe and secure authoritative DNS server
Upstream URL: https://trust-dns.org/
Keywords: trust-dns
Licenses: MIT, Apache
Conflicts: trust-dns, trust-dns-server
Provides: dns, dnskey-to-pem, get-root-ksks, pem-to-public-dnskey, trust-dns
Submitter: HLFH
Maintainer: HLFH
Last Packager: HLFH
Votes: 1
Popularity: 0.000000
First Submitted: 2022-11-28 15:37 (UTC)
Last Updated: 2023-08-03 21:33 (UTC)

Latest Comments

1 2 Next › Last »

HLFH commented on 2023-08-03 21:34 (UTC) (edited on 2023-08-03 21:35 (UTC) by HLFH)

@eclairevoyant Ok thanks, the package has been updated/fixed.

eclairevoyant commented on 2023-05-23 06:02 (UTC) (edited on 2023-05-23 06:03 (UTC) by eclairevoyant)

pkgver() currently generates an invalid version, I'd suggest using something similar to /usr/share/pacman/PKGBUILD-vcs.proto (only change was me adding s/^v//; and --tags):

git describe --long --tags | sed 's/^v//;s/\([^-]*-\)g/r\1/;s/-/./g'

I see @Hanabishi's comment about using mold to allow LTO, but mold -run cargo build (with LTO on) still seems to give the same error as before, not sure how to get that working.

HLFH commented on 2022-12-30 07:21 (UTC) (edited on 2022-12-30 07:22 (UTC) by HLFH)

@eclairevoyant trust-dns-git has been updated. LTO has been disabled within the PKGBUILD and will continue to be disabled until this is fixed.

eclairevoyant commented on 2022-12-25 17:06 (UTC)

This has nothing to do with devtools. All packages should build no matter which options are set in a user's own makepkg.conf. Therefore if a user happens to have LTO enabled, this PKGBUILD should override it. See wezterm's PKGBUILD for an example.

It literally hurts nothing to add it since you are already building with LTO disabled anyway??

HLFH commented on 2022-12-25 14:12 (UTC) (edited on 2022-12-25 14:17 (UTC) by HLFH)

It won't build apparently with LTO when LTO is enabled because of the use of devtools
which are the tools for the Arch Linux distribution for building and maintaining official repository packages
but not the AUR. By default, AUR maintainers only need to use core/pacman which does not have
its makepkg.conf file with LTO enabled. Shall AUR maintainers really care with LTO enabled/disabled
if core/pacman does not care about it? devtools is only part of the extra repository
and is therefore not default behaviour.

eclairevoyant commented on 2022-12-25 10:15 (UTC)

Which is exactly my point, it won't build with LTO so it should be disabled for this package.

HLFH commented on 2022-12-25 09:53 (UTC) (edited on 2022-12-25 09:54 (UTC) by HLFH)

Look, in core/pacman, makepkg.conf does not seem to have lto enabled.
But it seems that the makepkg.conf of Arch Linux devtools has lto enabled which I have not installed on my system.

eclairevoyant commented on 2022-12-24 23:07 (UTC) (edited on 2022-12-24 23:09 (UTC) by eclairevoyant)

I genuinely have no idea how you're able to build with LTO, unless you have some customizations in your makepkg.conf. Even the official wezterm package won't build due to this issue.

Just to confirm, can you try adding options=(lto) to this PKGBUILD and build in a clean chroot? I assume it won't build.

HLFH commented on 2022-12-20 11:41 (UTC)

@eclairevoyant The named binary has been removed upstream thanks to my PR.
So no more issues on that.

HLFH commented on 2022-12-15 12:23 (UTC) (edited on 2022-12-15 12:24 (UTC) by HLFH)

I also don't recommend to install the named binary that conflicts with the bind package.
Some people use this bind package only for dig and host utilities.
And overwriting the named binary would just create an unnecessary conflict.

1 2 Next › Last »