Include Multilib #125
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#125
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Is there a particular reason that this project doesn't include multilib packages?
I mean, they are mostly used for gaming (and run some older 32 bit applications) so they could definitily consume a significant amount of the used CPU time on a system - so kinda worth doing optimizations. :)
Sure, we can tackle that. Need to do dome researching, but it should not be that complicated.
Cool :)
What do we need to research? :)
Multilib builds use a different makepkg.conf iirc. Just need to adjust some flags and some logic choosing correct flags (e.g. which makepkg.conf to use; that's probably almost everything that needs to be done) for multilib repos.
This is an interesting observation:
Source: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=proton-ge-custom
Well, that does affect wine only as far as I can tell? No problems then, we can just exclude it (if that is even necessary, most people probably do not use system wine to launch games).
@anonfunc it doesn't affect wine at all, as wine will just not honer the system flags at all. :)
In this package the honering of system flags is patched in and they discovered why they are not honered :D
I feel like we should just try to build everything "as is" and have a look at the outcome.
As adding the multilib-repo to the system is a manual operation we can just flag it as experimental for a while, to make sure people just don't assume everything "just works" :)
Sounds good, I'll see when I have time to add it.
I added multilib support in
43db75f1f9
. I'll activate it as soon as the current buildcycle is finished.First
multilib
buildcycle finished. We'll test them for a couple of days, maybe a week, to make sure everything works as expected.If anyone wants to test them, add the new multilib repo above your current vanilla multilib entry in your pacman.conf: