then in cases where the patch does apply but would be diffede when 
running make-update, what is the regular build process doing?

i won't really worry about it. i'll just make sure to run everything the 
way i said in the last email from now on:

make patch

make update-patches

make

make update-plist

and to test: make package (i prefer to install from a package instead of 
doing make-install)

nevermind my question. i'll just do it this way from now on. by the way, 
thhe build has succeeded. it's just linking now. i'll test it soon, but 
i think this update is ready to go.



Am 01.09.26 um 13:28 schrieb Landry Breuil:
> Le Tue, Sep 01, 2026 at 01:19:27PM +0100, Leah Rowe a écrit :
>> Make update-patches confuses me. If it would produce a diff, but a ran it
>> after running make, does that mean when building a package, and patching, it
>> will do the equivalent of make update-patches just for applying them, but
>> not actually update them? (sort of like git cherry pick without error)
> i don't think i'm able to process that sentence.
>
> make update-patches (see infrastructure/mk/bsd.port.mk) looks for
> .orig.port files in $WRKSRC, and regens the patches. if you've made a
> new patch (cp x x.orig.port, edit x) it will pick it up. nothing else
> updates patches.
>
> you can run make update-patches anytime if you know your patches just to
> update the churn from code moving around/line changes, but sometimes
> (when PKG_SUBST is ran for example) you'd get some chunks modified, in
> the general case it's better to run it after make patch.
>
> make does call make patch as a dependency. make update-patches is never
> run as a dependency of another target, you need to run it manually.

-- 
Company director, Minifree Ltd
Registered in England, No. 9361826 | VAT No. GB202190462
Registered Office: 19 Hilton Road, Canvey Island, Essex SS8 9QA, UK

• OpenPGP_0x5C654067D383B1FF.asc (3K)