Package Base Details: linux-nitrous

Git Clone URL: https://aur.archlinux.org/linux-nitrous.git (read-only, click to copy)
Keywords: clang clearlinux kernel linux optimized
Submitter: superboringdev
Maintainer: superboringdev (n0m4n904)
Last Packager: superboringdev
Votes: 10
Popularity: 0.000010
First Submitted: 2019-11-05 16:41 (UTC)
Last Updated: 2024-05-02 17:20 (UTC)

Pinned Comments

superboringdev commented on 2020-03-23 19:25 (UTC) (edited on 2023-09-02 09:21 (UTC) by superboringdev)

The prebuilt kernel is built using Clang/LLVM 16.

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

[linux-nitrous]
Server = https://github.com/xdevs23/linux-nitrous/releases/latest/download/

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 the keys 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 7 8 Next › Last »

eschwartz commented on 2020-03-23 20:18 (UTC) (edited on 2020-03-23 20:19 (UTC) by eschwartz)

They're extremely useful for the Pacman repository, since pacman -U https://.../<filename>.pkg.tar.xz will validate those to make sure the binary product is signed, and repo-add could in theory be changed in future to use detached signatures rather than storing the .sig files as base64'ed blobs inside the linux-nitrous.db file (that's a topic for the pacman-dev mailing list though).

It's just they're not very useful to the PKGBUILD which isn't doing anything with them. :D

superboringdev commented on 2020-03-23 20:10 (UTC)

Oh I'm sorry, I didn't notice that those were pushed as well, I just removed them and adjusted the .gitignore file accordingly. Sorry for that!

Should I keep uploading them to the repository itself though or are they redundant there as well?

eschwartz commented on 2020-03-23 20:07 (UTC)

They are redundant, and redundant things waste time and space and clutter up git log.

But also binary files don't compress well in git, and the AUR has checks to deny pushes of files that are above a certain limit... but allowing kernel .config and other moderate sized files is a balance we have to strike, so sometimes things sneak in, often by accident. We'd prefer to keep the server disk usage down where possible. Hence it would be greatly appreciated to prevent any more of these from getting uploaded.

Thanks!

superboringdev commented on 2020-03-23 19:55 (UTC)

@eschwartz I can remove them from the script I use to upload those files.

Is it bad that they are uploaded or are they just redundant? AFAIK they only contain the signature but since I don't have a lot of experience in these kind of things, I'm not too sure about it.

eschwartz commented on 2020-03-23 19:50 (UTC) (edited on 2020-03-23 19:51 (UTC) by eschwartz)

Hey -- you're accidentally committing .pkg.tar.xz.sig files to git. Can you please add this to your .gitignore?

superboringdev commented on 2020-03-23 19:25 (UTC) (edited on 2023-09-02 09:21 (UTC) by superboringdev)

The prebuilt kernel is built using Clang/LLVM 16.

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

[linux-nitrous]
Server = https://github.com/xdevs23/linux-nitrous/releases/latest/download/

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 the keys before being able to install my packages:

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

superboringdev commented on 2020-03-15 17:46 (UTC)

@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 (UTC)

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 (UTC)

@eschwartz

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.