> Also fine with some note that, if you want to fork lucene and make your > own source release, you can use our packaging build infrastructure, but you > need to git clone. We are giving you a source release, not a git clone > (shallow or deep). If you want to fork and make your own customized source > releases, use git to clone. It will probably be easier on you in the long > run to use version control for your fork, because then you can merge > upstream changes too. >
It's actually quite simple to make it compilable from sources by adding a "fake" git hash stored with the source distribution - I played with it. In the end, I decided the value of this is so marginal that it's not worth the extra maintenance cost. The build itself still works (git version is set to 'unknown', as far as I remember) - it is the "distribution" targets that fail and I'm fine with it. Dawid
