re: LICENSE being slightly different in the source tarball
Here at SimuQuest, we've had similar confusions between files which are
templates in version control but fleshed out in the release.
Our solution has been to
* keep the templates in a separate folder
* use a templating language like the one in maven or Velocity
* try to keep comments in each file saying what it is and where it came
* not include the template folder in the binary release
For us, this has been motivated less by tarball comparisons and more by
wanting developers to modify and commit the "right" copy of the file.
Hope the info helps.
On Fri, Feb 9, 2018 at 5:39 AM, Neil C Smith <neilcsm...@apache.org> wrote:
> On Fri, 9 Feb 2018 at 10:30 Bertrand Delacretaz <bdelacre...@apache.org>
> > I think LICENSE being slightly different (better actually, right?) in
> > the source tarball is perfectly fine if there's a rational reason for
> > it - you just need to reassure people that it's not a mistake.
> Thanks. Yes it's better - to clarify I meant aiming towards checking in
> and tracking history in git of the version in the full source bundle.
> Something for a later discussion anyway.
> > For that you just need to be able to answer such questions with "have
> > a look at http://netbeans.apache.org/release-management.html" instead
> > of re-explaining every time.
> Definitely one to add to the list of initial pages we were discussing the
> other day then! ;-)
> Thanks and best wishes,
> Neil C Smith
> Artist & Technologist
> Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org