You are not logged in.
Hi all,
I'm posting to see if anyone is interested in a tool I use regularly. I have created a bash script for automatic building in a clean chroot. I use it to maintain my AUR pkgs when I update them. I've found it saves me time and screwing around.
This script (more or less) performs the steps outlined in the DeveloperWiki page Building in a Clean Chroot -- Classic Way.
If this is of general interest I am happy to share it on the wiki, perhaps under that DeveloperWiki page? Thanks for your feedback
Clemmitt Sigler
Last edited by cmsigler (2022-11-29 13:15:33)
Offline
What advantages does your script have over simply running extra-x86_64-build from the devtools package?
Offline
What advantages does your script have over simply running extra-x86_64-build from the devtools package?
Good question! Perhaps none. When reading that DeveloperWiki page I didn't try extra-x86_64-build because I got the impression it wouldn't work for an AUR pkg. I thought it was just for pkgs in the extra repository. Let me look at this....
OK, I will play with extra-x86_64-build to see if it does exactly the same thing. Thank you for the heads-up!
Clemmitt
Offline
I was also surprised when I learned this could be used for other packages not in extra, but I have been using it for buildtesting packages and it works with any PKGBUILD.
Offline
it works with any PKGBUILD.
Not exactly, try building a lib32-* package with extra-x86_64-build .
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
icar wrote:it works with any PKGBUILD.
Not exactly, try building a lib32-* package with extra-x86_64-build .
Ok, let's pretend 32 bit packages don't exist ?
Offline
What advantages does your script have over simply running extra-x86_64-build from the devtools package?
This morning I finally made time to test a good use case for building an AUR pkg in a clean chroot. This PKGBUILD requires a separate AUR pkg as a depend, which means a pre-built pkg must be specified as a '-I pkg-name-1.2-3-x86_64.pkg.tar.zst' argument.
And, indeed, using extra-x86_64-build works!!! For this case, do something like the following:
$ mkdir ~/my_AUR_dir/tmp
$ mkdir ~/my_AUR_dir/AUR_deps
$ cp ~/some_dir/pkg-name-1.2-3-x86_64.pkg.tar.zst ~/my_AUR_dir/AUR_deps/
$ cp ~/some_other_dir/PKGBUILD ~/my_AUR_dir/tmp/
$ cd ~/my_AUR_dir/tmp/
$ extra-x86_64-build -c -r ~/my_AUR_dir/tmp/ -- -I ~/my_AUR_dir/AUR_deps/pkg-name-1.2-3-x86_64.pkg.tar.zst
@Slithery, thank you for the tip!
Offline
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
... I did not know about this pkg
@graysky Thank you for this heads-up!
Clemmitt
Offline
Hi again,
Well, I have tilted at the windmills of posting a note about using extra-x86_64-build for AUR pkgs, both on the AUR and the DeveloperWiki Building in a clean chroot wiki pages. I have been reverted or rejected by maintainers twice. Fair enough. So, given the power of modern search engines, I say...
AUR MAINTAINERS!!! Hear, ye!!! Use extra-x86_64-build from the devtools pkg to test build your pkgs in a clean chroot!!! DON'T REINVENT THE WHEEL LIKE I DID!!!
(Humor FULLY intended!)
Clemmitt
Offline