Developers • About Git overrides

Trying to wrap my head around all this. I did this:

Code:

#!/bin/shgit clone --depth 1 --branch "9.0.0.p44" "git@github.com:Zimbra/zm-build.git"cd zm-buildENV_CACHE_CLEAR_FLAG=true ./build.pl \  --ant-options -DskipTests=true \  --git-default-tag="9.0.0.p43,9.0.0.p42,9.0.0.p41,9.0.0.p40,9.0.0.p39,9.0.0.p38,9.0.0.p37,9.0.0.p36,9.0.0.p34,9.0.0.p33,9.0.0.P33,9.0.0.p32.1,9.0.0.p32,9.0.0.p30,9.0.0.p29,9.0.0.p28,9.0.0.p27,9.0.0.p26,9.0.0.p25,9.0.0.p24.1,9.0.0.p24,9.0.0.p23,9.0.0.p22,9.0.0.p21,9.0.0.p20,9.0.0.p19,9.0.0.p18,9.0.0.p17,9.0.0.p16,9.0.0.p15,9.0.0.p14,9.0.0.p13,9.0.0.p12,9.0.0.p11,9.0.0.p10,9.0.0.p9,9.0.0.p8,9.0.0.p7,9.0.0.p6,9.0.0.p5,9.0.0.p4,9.0.0.p3,9.0.0.p2,9.0.0.p1,9.0.0" \  --build-release-no="9.0.0" \  --build-type=FOSS \  --build-release="KEPLER_T090000p43C090000p44FOSS" \  --build-thirdparty-server=files.zimbra.com \  --no-interactive \  --build-release-candidate=GA \  --git-overrides maldua-pimbra.url-prefix="git@github.com:maldua-pimbra" \  --git-overrides zm-web-client.remote="maldua-pimbra" \  --git-overrides zm-web-client.tag="9.0.0.p44-maldua"

Seems like magic! I can see a lot of future functionality in this.

Git overrides, either in the form of command line switches or config.build contents have been there in zm-build since ever. You can check default config.build.in contents.

It's probably used by Zimbra developers everyday so that an specific core repo is not fetched from default sources but from their own local repo which might have new features or fixes to be implemented.

So, yeah, I mean, if you want to explore wild customizations on core Zimbra packages that's one of the cleanest ways of doing it.

The only new thing here is --git-overrides being integrated onto ZCS build wrapper scripts so that some of the Zimbra core packages are not strictly from official upstream repos.

Ianw1974's zimbra-build-scripts uses an alternate method of applying changes based on a patches directory but, you know, unless it's strictly a Debian package I don't like keeping track of several patch files. I prefer to maintain git commits on branches.

Statistics: Posted by adrian.gibanel.btactic — Sat Mar 22, 2025 8:42 pm

---