SILO-GROUP
/
Dyad
forked from Dark-Horse-Linux/pyrois
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

Consider centralized patch management #1

New Issue
Open
opened 2024-02-11 20:54:17 +00:00 by Phanes · 0 comments
Phanes commented 2024-02-11 20:54:17 +00:00
Owner

During updates of package versions, the patches for those versions will also change.

This introduces a small source management problem. The build process for these packages does not really change, but, the patches themselves will at times, and, going through every build script for each package update is time consuming, almost purely due to patching.

Consider introducing a patch management scheme that takes in the package name, version, and pass identifier so that which patches get applied to which versions are managed in one place instead of spread out throughout the package build scripts.

The tradeoff is the package scripts are no longer standalone for their intended function, so, this warrants both consideration and opposition.

During updates of package versions, the patches for those versions will also change. This introduces a small source management problem. The build process for these packages does not really change, but, the patches themselves will at times, and, going through every build script for each package update is time consuming, almost purely due to patching. Consider introducing a patch management scheme that takes in the package name, version, and pass identifier so that which patches get applied to which versions are managed in one place instead of spread out throughout the package build scripts. The tradeoff is the package scripts are no longer standalone for their intended function, so, this warrants both consideration and opposition.
Phanes changed title from Introduced centralized patch management to Consider centralized patch management 2024-02-11 20:55:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
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: SILO-GROUP/Dyad#1
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?