FYI I'm working integrating the feedback and working towards the next RC. I started working on build instructions and things were getting quite complex while building from source, and adding steps like the os-level deps, creating the `.po` files, building the JS, and these instructions tend to not be perfectly reproducible across environments, so I decided to write a Dockerfile that builds from source instead of docs or a bash script. Eventually that can evolve to run assertions on the build (running tests, checking keys, ...) in a reproducible fashion. The built package can be extracted from the docker image, or the Dockerfile can be used as a reference if someone needed to make an equivalent bash script.
Similarly, I'm thinking about using a Dockerfile for the process of packaging the source release, since the process forces a "git clean" that can be harmful to existing environments. Max On Sat, Apr 27, 2019 at 1:40 AM <jus...@classsoftware.com> wrote: > Hi, > > > - they are not? I dont follow? How would you suggest making them binary > then? > > Ask on legal discuss, I don’t think they will be allowed in a source > release, but it may be possible given maps are not likely to change much. > Worse case you may have to find some maps under a different license or ask > for them to be relicensed under a more friendly license. > > > On the other hand the initial picture you painted seemed quite grim but > these issues can be overcome relatively easy. > > All of the issues are easy to fix one way or another, this stuff is hard > to get right first time around, but gets easier. > > Thanks, > Justin > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
