Consider centralized patch management #1

New Issue

Phanes · 2024-02-11T15:54:17-05:00

Phanes commented

2024-02-11 15:54:17 -05:00

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 15:55:35 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SILO-GROUP/dyad#1