Package Details: linux-xanmod-edge-linux-headers-bin-x64v4 6.11.1-1

Git Clone URL: https://aur.archlinux.org/linux-xanmod-edge-linux-bin-x64v4.git (read-only, click to copy)
Package Base: linux-xanmod-edge-linux-bin-x64v4
Description: The Linux kernel and modules with Xanmod patches - Rolling Release (EDGE) - Prebuilt version - x64v4
Upstream URL: http://www.xanmod.org/
Licenses: GPL2
Conflicts: linux-xanmod-linux-bin-x64v4
Provides: linux-xanmod-edge
Replaces: linux-xanmod-edge, linux-xanmod-linux-bin-x64v4
Submitter: SoftExpert
Maintainer: SoftExpert (figue)
Last Packager: SoftExpert
Votes: 0
Popularity: 0.000000
First Submitted: 2023-08-29 06:20 (UTC)
Last Updated: 2024-09-30 17:45 (UTC)

Pinned Comments

SoftExpert commented on 2024-11-29 17:53 (UTC)

x64v4 builds are no longer provided - there is no difference in the CPU instruction set between x64v3 and x64v4, so the x64v4 are no longer justified. Obviously if Xanmod decides to provide this flavor again, we will deliver it.

Latest Comments

SoftExpert commented on 2024-11-29 17:53 (UTC)

x64v4 builds are no longer provided - there is no difference in the CPU instruction set between x64v3 and x64v4, so the x64v4 are no longer justified. Obviously if Xanmod decides to provide this flavor again, we will deliver it.

SoftExpert commented on 2023-09-29 05:23 (UTC)

Xanmod issues now 3-4 releases under the tag EDGE, and then stops because the MAIN tag takes over.

As an example, we had 6.5.0, 6.5.1 and 6.5.2 as EDGE. Then 6.5.3 was issued under MAIN.

The binaries naming does not make distinction between EDGE and MAIN, so if we build both EDGE and MAIN out of the same binaries, it would be impossible to have both lines installed at the same time (binaries from one would tend to replace the binaries of the other). We had to put a conflicting clause in the package because of that.

Would you prefer to have EDGE to continue to be built, even though the same binaries would be used for MAIN ?