You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose to have configuration files to substantially reduce the need for patches, as patches are brittle. As can be seen from recent GHC update, version updates require recommitting of patches as they contain version numbers.
Patches are a good idea because they are universal and allow any type of modification. However, it turns out that most often the only changes needed are changes to the list of dependencies detected by cblrepo. So I propose someting like patches/<pkgname>.override with
depends=+foo -bar +baz
So this information is applied internally by cblrepo to its detected list of dependencies before generation of PKGBUILD and it doesn't contain version numbers so there is no need to maintain it on every update. Then patching proceeds as usual.
The .override files are technically not patches, but putting them in patches/ lets a user to uniformly inspect/remove all overrides by ls patches/<pkgname>.*, rm, vim -p etc. And the config can be extended to support overrides other from depends if we ever decide so.
The text was updated successfully, but these errors were encountered:
#32 will reduce the number of cases where we need manual patching. But I think it will still fail sometimes (for example for non-library dependencies). This #35 feature will make maintenance of patches easier in many cases. I understand the two features as independent improvements.
I propose to have configuration files to substantially reduce the need for patches, as patches are brittle. As can be seen from recent GHC update, version updates require recommitting of patches as they contain version numbers.
Patches are a good idea because they are universal and allow any type of modification. However, it turns out that most often the only changes needed are changes to the list of dependencies detected by
cblrepo
. So I propose someting likepatches/<pkgname>.override
withSo this information is applied internally by
cblrepo
to its detected list of dependencies before generation of PKGBUILD and it doesn't contain version numbers so there is no need to maintain it on every update. Then patching proceeds as usual.The
.override
files are technically not patches, but putting them inpatches/
lets a user to uniformly inspect/remove all overrides byls patches/<pkgname>.*
,rm
,vim -p
etc. And the config can be extended to support overrides other fromdepends
if we ever decide so.The text was updated successfully, but these errors were encountered: