glibc might not be build to avoid breakage #41
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#41
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?
Since glibc is part of pacman dependencie, we might not build it to avoir possible breackage of pacman
That is why it's somewhat useless to have pacman on the blacklist: we would need to exclude all dependencies to make it fully excluded and avoid breakage.
But to be honest I want to have a x86-64-v3
glibc
, since its so commonly used.Maybe it would be better to write a FAQ about how to install/download
pacman-static
from Eli than to have pacman blacklisted, but I'm not sure yet.I decided to remove
pacman
from the blacklist. ALHP seems pretty stable since introducing dependency resolving before building, so I feel confident enough so build pacman. Besides, like above mentioned, it is pointless without excluding glibc as well.