Check commit time before building package #195

Open
opened 2022-05-24 10:29:25 +02:00 by Jef Roosens · 1 comment

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.

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.
Jef Roosens added the
idea
label 2022-05-24 10:29:25 +02:00

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.

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.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#195
There is no content yet.