| Git Clone URL: | https://aur.archlinux.org/linux-nitrous.git (read-only, click to copy) |
|---|---|
| Package Base: | linux-nitrous |
| Description: | Header files and scripts for building modules for Linux kernel (tagged git version) |
| Upstream URL: | https://gitlab.com/xdevs23/linux-nitrous |
| Keywords: | clang clearlinux kernel linux optimized |
| Licenses: | GPL2 |
| Submitter: | superboringdev |
| Maintainer: | superboringdev (n0m4n904) |
| Last Packager: | superboringdev |
| Votes: | 11 |
| Popularity: | 0.26 |
| First Submitted: | 2019-11-05 16:41 (UTC) |
| Last Updated: | 2024-11-17 18:18 (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.
If your PKGBUILD contained the two lines:
sudo pacman -U https://github.com/xdevs23/linux-nitrous/releases/download/v5.5.9-1/linux-nitrous-git-5.5.9-1-x86_64.pkg.tar.xz
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.
@eschwartz
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.
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: https://wiki.archlinux.org/index.php/Unofficial_user_repositories
-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.
@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?
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.
@toki1990 Install linux-nitrous-headers pkgbuild
thanks you, works perfect
!!! Important for nvidia-dkms users !!!
Please wait for the release of an updated nvidia-dkms package (probably the one in testing channel, 440.44-16) otherwise you won't be able to make the nvidia driver work with this (5.5)
Alternatively, as a workaround, edit /etc/pacman.conf, move the testing repository to the very bottom and uncomment it. Then just pacman -Syu testing/nvidia-dkms
(1/1) yükleniyor linux-nitrous [-----------------------] 100%
Updating module dependencies. Please wait ... Generating initial ramdisk, using mkinitcpio. Please wait... /usr/bin/mkinitcpio: satır 265: /etc/mkinitcpio.d/linuxlinux-nitrous.preset: Böyle bir dosya ya da dizin yok ==> ERROR: Failed to load preset: `/etc/mkinitcpio.d/linuxlinux-nitrous.preset' hata: komut düzgün çalıştırılamadı linux-nitrous için opsiyonel bağımlılık(lar) linux-nitrous-headers: to build DKMS modules against this kernel :: Bağlantılı işlemler listesi çalışıyor... (1/2) Arming ConditionNeedsUpdate... (2/2) Updating module dependencies...
Pinned Comments
superboringdev commented on 2020-03-23 19:25 (UTC) (edited on 2024-09-16 19:48 (UTC) by superboringdev)
The prebuilt kernel is built using Clang/LLVM.
The linux-nitrous binary package can be installed by adding following lines to your /etc/pacman.conf:
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: