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
Currently you should manually track whether the patch has already been applied, or use the patches attribute of the recipe to set the patches (in which case this is done, and the patches applied, automatically). If any existing recipe doesn't do this (are you looking at openssl?), it's a bug.
The patch in the openssl recipe is applied to files generated by the Configure script, which is why it runs unconditionally. Any patches applied via the patches class attribute are tracked and will only be applied once.
Activity
inclement commentedon Feb 9, 2016
Currently you should manually track whether the patch has already been applied, or use the
patchesattribute of the recipe to set the patches (in which case this is done, and the patches applied, automatically). If any existing recipe doesn't do this (are you looking at openssl?), it's a bug.kived commentedon Feb 9, 2016
The patch in the openssl recipe is applied to files generated by the Configure script, which is why it runs unconditionally. Any patches applied via the
patchesclass attribute are tracked and will only be applied once.brussee commentedon Feb 9, 2016
The patches can only be applied after a certain step in the recipe. When exactly are the patches = [] applied?
Yes, as a matter of fact I took the openssl recipe as an example.
kived commentedon Feb 9, 2016
They are applied directly following
prebuild_arch.brussee commentedon Feb 9, 2016
Actually, the patches that are affected by the rollback can and should go in the patches = [].
Thanks!