Package Base Details: linux-nitrous

Git Clone URL: (read-only, click to copy)
Keywords: clang clearlinux hardened kernel linux optimized wireguard zen
Submitter: superboringdev
Maintainer: superboringdev
Last Packager: superboringdev
Votes: 7
Popularity: 0.22
First Submitted: 2019-11-05 16:41
Last Updated: 2021-04-16 14:28

Pinned Comments

superboringdev commented on 2020-03-23 19:25

The prebuilt kernel is built using Clang/LLVM 11.

The linux-nitrous binary package can be installed by adding following lines to your /etc/pacman/pacman.conf:

Server =

Then you can install the package using your AUR helper or pacman (e. g. sudo pacman -Syu linux-nitrous linux-nitrous-headers)

You probably need to add my key before being able to install my packages:

sudo pacman-key --recv-keys E9C2DECAC962CB3AF1376D44148A9E3C9C3E3BF0
sudo pacman-key --lsign-key E9C2DECAC962CB3AF1376D44148A9E3C9C3E3BF0

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

superboringdev commented on 2020-03-15 17:46

@eschwartz Thanks for clarifying. I will take a look at it and move the prebuilt package to a custom repository when I have more free time to spare. After that, this one will be changed to a build-from-source repository and I'll notify users using a pinned comment.

eschwartz commented on 2020-03-15 17:43

Custom repositories are faster to set up than initializing your AUR helper, running makepkg, having makepkg expensively check your PKGBUILD for syntax errors, copy files around the filesystem, re-tar the files, and run a compression program on the results.

The compression stage alone is a major time sink.

Adding a custom repository consumes one interactive experience with a text editor, and then takes no time at all for future updates. Just a teeny bit of prep work pays off big time for the future.

(re: clutter, you are under no obligation to add a custom repo to the Unofficial User Repositories wiki page in addition to mentioning it here. Just mention it here, if you like.)

superboringdev commented on 2020-03-15 17:31


I don't think it's a good idea to run sudo inside the PKGBUILD as the AUR helper doesn't want to be run as root and thus anything inside it shouldn't either.

I think an AUR package has more reach than a custom repository. Custom repositories also take more time to set up than simply issuing a command like <AUR helper> -S linux-nitrous. I also think that having a custom repository for just one package is kind of overkill and only adds clutter to the repository list.

eschwartz commented on 2020-03-15 17:26

If your PKGBUILD contained the two lines:

sudo pacman -U
exit $?

then it would certainly directly utilize the downloaded package rather than repacking it.

(Do I need to explain why this is not a valid use of the AUR?)

Please explain why you don't think it is acceptable to ask users to add a custom repository. A custom repository is much more streamlined and integrated, and provides a superior user experience for upgrading, over using an AUR helper.

superboringdev commented on 2020-03-15 16:56


That's not the approach I want to go for.

The prebuilt package should be available on the AUR so that people can easily install and update it without having to add any custom repositories. The only thing I'd be willing to do is to change the PKGBUILD in a way that it directly utilizes the downloaded pkg instead of repacking it.

I should also think about how I am going to transition this package since people who have this package installed will suddenly be building it from source which takes a long time depending on your system resources.

eschwartz commented on 2020-03-15 16:50

No, please don't rename it to a -bin package. Please do change this package to build from source, then, since you are upstream and you provide a prebuilt .pkg.tar, you can add a pinned comment here which links to your repository which can be added to pacman.conf, and which allows users to pacman -Syu and sync your existing package.

You can also add it to the index here:

-bin packages are intended to repack binaries which are not in pacman format, so that they can be installed via pacman. It is misuse to use them to repack a binary which is already in pacman format, when custom repos exist for this exact purpose.

superboringdev commented on 2020-03-15 13:31

@Xyne Thanks for your feedback. I'll have to rename the packages then. Do you know how to directly install the pkg file without having to repack it? I haven't found a solution for that yet.

Currently, the packages are as follows:

linux-nitrous: prebuilt

linux-nitrous-git: built from the current branch (right now v5.5+)

According to your information and the conventions used on the AUR:

linux-nitrous-bin: prebuilt (same sources as linux-nitrous)

linux-nitrous: built from a tag, for example v5.5.9-1

linux-nitrous-git: built from the current branch — this one stays the same as before

Is this what you mean?

Xyne commented on 2020-03-15 13:01

It's unconventional to have a PKGBUILD that downloads a pacman package and just repacks it to obtain an equivalent package. The user may as well just download the original package. I'm not convinced that the redundancy is worth it just to have it in the AUR.

Regardless, the name of the package should be suffixed with "-bin" because it is using pre-compiled sources. If you wish to keep using the current approach, please rename the package to "linux-nitrous-bin" and add "linux-nitrous" to the "provides" and "conflicts" arrays.

The current (non-bin) package should build from source using a PKGBUILD equivalent to the one used upstream to build the package that you're repacking.

DarkMind commented on 2020-03-10 18:55

@toki1990 Install linux-nitrous-headers pkgbuild

DarkMind commented on 2020-03-10 18:54

thanks you, works perfect