AUR - how the hell? #43
Comments
|
Ah, yes, the When I was doing Arch builds, I had to run a Check this: pauldotknopf/darch-recipes@2945b2d#diff-844c94b0e5d70e755e1d75768823c931 |
|
Looks like there's been a quite a few changes to makepkg since this - the patch won'y apply as is. Sigh - this is so much harder/more work than it should be - they really should provide an option to allow running as root... I did try and get trizen to build the package and then install it via pacman, but that just caused other headaches due to write permissions problems among other things... |
|
Might have got it working with a super simple patch that just removes the root check. It's running now and it certainly runs as root, so, unless there are some build implications I'm unaware of, it's looking good. |
Absolutely. I suggested to make it overridable via environment variables, and the maintainers basically said fuck you. I really hate the Arch community and their collective attitude. I recommend Ubuntu! :) |
|
Ubuntu would certainly be easier, but it makes too many choices for me that I don't like. That's what I love about Arch - I can set up the system pretty much exactly how I want it. |
|
It seems that whatever I've did to makepkg (literally just removed the root check - or so I thought...) has now caused damage to my system. To be fair, they did warn me... :-( I'm going to reopen this because, even if I never get past it, it's still likely to affect other users. |
|
Details on what happened? |
|
I started getting issues with files no longer owned by packages ( which then caused problems with installing/upgrading packages because the files were already there...), or files not being found that should've been. All the problems went away as soon as I booted an image - which you'd expect, but they started to appear again when I ran trizen - which in turn ran my patched makepkg. |
|
Another option is to create a dummy user to build the packages in Darch, using gosu or something. |
|
You can see the script I'm using for the commonly used "common"here
which is completely baffling me - why on earth is the BUILDDIR being set to /? nobody definitely has write permissions on /home/build/trizen I'm sure this is much harder than it needs to be... |
|
Lol. Just use Ubuntu and never have a problem again! ;) |
|
And never have my system how I like it again either 😜 |
|
Honestly, out of curiosity, I'd love to see a detailed breakdown of what customizations you can do in arch that you can't do in Ubuntu. |
|
Ubuntu with Bedrock Linux? 😹 |
|
As far as I'm aware Ubuntu won't ever give me a super basic setup after the installation and will always try and install a bunch of packages I don't want. |
|
Ubuntu will only install a bunch of packages when you install You can blacklist then though, like I do here: https://github.com/pauldotknopf/darch-recipes/blob/master/recipes/desktop/blacklist-packages |
Having now managed to get a basic build running I'm now trying to work on some further images intended for other computers, but I'm banging my head against a brick wall when it comes to aur packages.
I don't really care too much about build times, so I don't want to bother with maintaining and hosting my own pacman repository, but, whenever I try and build a packge in a script, I run into the issue that trizen/makepkg cannot be run as root, but pacman must be. I have pacman enabled via sudo, but, because the script itself is run as root, this then causes other issues.
Is anyone else building packages during image builds? How do you handle it?
The text was updated successfully, but these errors were encountered: