Significant install size differences #108
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#108
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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?
I noticed that on a couple of packages the install size reported by pacman is significantly different compared to the regular repo ones:
While I yet not encountered an issue with the packages (as far as I'm actually using them) - it might be worth given a look what's going on in them (and maybe exclude them from pushing to the mirror if a build process is creating massively different sizes - if not manually checked).
This is probably a side-effect of
-O3
and can be safely ignored.Interesting. I wouldn't expected THAT much of a difference 🤔
Just an idea, could you run an -O2 compile for those packages on the list (fairly easily) on the build machine - just to be sure that there's nothing else going on?
Would take a long long time on my available hardware :'D
I don't think much more needs to be said here at the moment. If anything comes up, please reopen.