Dependency-oriented build order #14
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?
Currently, ALHP builds all updated packages (or
PKGBUILD
s to be exact) to [core], [extra] and [community] as soon as they are in their respective/repo
folder in randomized order.What ALHP should do instead:
(make-)depends
(doesn't have to be a tree, sorted list would do the same on a functional level)Never mind, I just realized that since we build in a clean chroot with (hopefully, depends on the mirror somewhat) up to date packages from [core], [extra] and [community], this should be no problem.
It would be a problem if we use x86-64-vN packages as chroot sync mirror, which we don't.
What we should do instead is check if packages in
(make-)depends
are the lastest ones from the repo, and our mirror is not lagging behind or try again later if he does.