Hi Makoto
I build Doris successfully in ubuntu xenial's docker container on OSX.
Beside software that you have installed, I installed `apt-get install g++
ant cmake zip byacc flex automake libtool binutils-dev libiberty-dev bison
python2.7 libncurses5-dev lsb-core patch xz-utils`
The error messa
Yup. This seems concordant with most of the GPL exception clauses on
generated output. That is fine, we don't prohibit through use of GPL for
target architecture buildable tarballs of sources, so long as the consumers
of those source tarballs are not imposed restrictions beyond the AL 2.0.
Many pr
Hi,
While I would not oppose it going forward I think the podling could still do
with another experienced mentor. Any takers?
Reason why I think this is below, please don’t take this personally or if you
think it’s inaccurate speak up, I just want to give this new podling a good
chance at succ
Hi Justin,
Can you please chime in here on next steps?
Thanks
Vinoth
On Tue, Jan 8, 2019 at 3:53 PM Vinoth Chandar wrote:
> Here is the new list.
>
> * Luciano Resende (lresende at apache dot org)
> * Thomas Weise (thw at apache dot org
> * Kishore Gopalakrishna (kishoreg at apache dot org)
Moving this to the Doris dev list - general@incubator is BCC’d.
Regards,
Dave
> On Jan 10, 2019, at 10:23 AM, Makoto Yui wrote:
>
> Reed,
>
> Why not cancel rc1 and create rc2 fixing license header issue that Willem
> pointed?
> It seems it's better to be fixed.
>
> It also seems that no one
Reed,
Why not cancel rc1 and create rc2 fixing license header issue that Willem
pointed?
It seems it's better to be fixed.
It also seems that no one from IPMC succeeded to build distribution from
src (no sure for Luke though).
I got the following build error (which might be gcc-5 version issue):
+1 binding
Best Regards!
-
Luke Han
On Thu, Jan 10, 2019 at 2:51 PM Li,De(BDG) wrote:
> Hi,
>
> Does anyone help us to check and vote？
> Now we got two +1(binding).
> If needed we will cancel and call for next VOTE after fixed all issues
> which Willem and Justin mentioned
Hi,
> Hi Justin, it would be great if we can clarify the policy the submodule
> dependencies.
Basically follow the guiding principle [1] what states anything that is bundled
in a release need to be mentioned in LICENSE. If it not in the release then it
doesn’t need to be included.
Thanks,
Jus
Hi Justin, it would be great if we can clarify the policy the submodule
dependencies.
Strictly speaking, these dependencies are in the form of git submodule and
they are not part of the commit tree (instead, they are pointers to the
specific version of dependency).
If we just do git clone, or tag
