Rebuild on updated dependencies #293
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#293
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 recent openssl update broke a lot of my packages. The update occured right after my Vieter instance rebuilt all of my packages, causing them to all become broken.
As a solution, I propose adding a relatively frequent check to see whether any of the dependencies of the package have changed and if so, to rebuild the package earlier than its regularly scheduled time.
I'm afraid this will add a lot of complexity to Vieter however, as it would require us to store all dependencies used to build a package.
Thanks to now being able to schedule forced builds, this isn't as big of a priority. In the case of big breakage, the user could simply force-build all packages.