Closed lz00qs closed 1 year ago
Knowing this is a incorrectly opened PR, I still have some points here:
native_build
method is unmaintained after I switched the repo to cross_nobuild
as I started to host my own package repo. It had some un-fixed overlooked issues, notably about package rebuilding. It should work as how it worked before the switch, but I won't fix it if it breaks in the future.Knowing this is a incorrectly opened PR, I still have some points here:
- The
native_build
method is unmaintained after I switched the repo tocross_nobuild
as I started to host my own package repo. It had some un-fixed overlooked issues, notably about package rebuilding. It should work as how it worked before the switch, but I won't fix it if it breaks in the future.- If you're creating your own distro-packing repo, I don't recommend to base that repo on any of my repo, rather you should create a new one instead of forking from my repo, as you shouldn't need device-specific codes here, all they do is messing up your project structure and history. E.g. orangepi5-archlinuxarm lies in its own repo
- If your kernel package is stable and you decide to push that to AUR, you can open a PR on my archrepo to add it to the aarch64 build list. First of all, sorry for my reckless merge request. Thank you very much for the reminder, my current development goal is to adapt Archlinux to the orangepi zero3 I have, I'll take your suggestion into consideration when I've got the bootloader related packages and kernels available!
First of all, sorry for my reckless merge request. Thank you very much for the reminder, my current development goal is to adapt Archlinux to the orangepi zero3 I have, I'll take your suggestion into consideration when I've got the bootloader related packages and kernels available!
Hello, I have recently changed a few things in both this and orangepi5 project, and I think downstream should be notified of them. But since you're the only active downstream I'll just write here.
merge dev