Check commit time before building package #195
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vieter-v/vieter#195
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
The current method of first letting makepkg generate the pkgver works just fine, but does require the server to download all the dependencies first. For packages specifying a specific version (so not a
-git
package), the build container could either check whether the latest commit is newer than the last time the package was successfully built, or at least check the version before installing the dependencies.Not sure how we would detect whether a package is a development package or not; I'll have to research that.
A package could be marked as either a development package or a proper release package, defined by a
-stable
&-dev
CLI flag. Packages that are not explicitely marked as being a stable package will let makepkg calculate the pkgver, while the others will check the Git commit version (or perhaps the version defined .SRCINFO) instead. For packages that download large files as sources or require lots of dependencies, this could greatly reduce their time spent on unnecessary builds.