heron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Graham <billgra...@gmail.com>
Subject Re: Mentor question about third_party cpp binary deps
Date Tue, 25 Jul 2017 17:54:37 GMT
I'm researching this issue internally and will report back.

On Mon, Jul 24, 2017 at 2:11 PM, Karthik Ramasamy <karthik@streaml.io>
wrote:

> Bill -
>
> These artifacts will not be in maven since some of the C++ projects. But
> bazel does provide a way download these tarballs from the web and compile
> them. Is there a way to internally setup an environment for third party cpp
> tarballs?
>
> cheers
> /karthik
>
> On Fri, Jul 21, 2017 at 10:39 AM, Bill Graham <billgraham@gmail.com>
> wrote:
>
>> Thanks Jake for the pointer. Karthik is it possible to pull those
>> artifacts
>> from maven? Twitter's internal build environment is closed, with only
>> access to a maven and pypi proxy, so pulling packages from http locations
>> on the web will not work.
>>
>> On Fri, Jul 21, 2017 at 5:50 AM, Jake Farrell <jfarrell@apache.org>
>> wrote:
>>
>> > Hey guys, just getting back from vacation, sorry for any delay in
>> > responses from my end.
>> >
>> > A source release must contain no binary objects. Full details are
>> > available on the ASF release policy page [1].
>> >
>> > Bazel can download them, http_file should be what you need.
>> >
>> > -Jake
>> >
>> >
>> > [1]: http://www.apache.org/legal/release-policy.html
>> >
>> >
>> > On Fri, Jul 21, 2017 at 7:02 AM, Karthik Ramasamy <karthik@streaml.io>
>> > wrote:
>> >
>> >> FYI - If the binary tar balls need to be removed, I believe bazel has a
>> >> way
>> >> to download these files
>> >> and compile them. Let me investigate and report back.
>> >>
>> >> On Thu, Jul 20, 2017 at 2:07 PM, Bill Graham <billgraham@gmail.com>
>> >> wrote:
>> >>
>> >> > Hi,
>> >> >
>> >> > In the incubator vote thread John mentioned the following:
>> >> >
>> >> > - The contents of
>> >> > > https://github.com/twitter/heron/tree/master/third_party seems
>> >> > > to be mostly binary files, and you'll need to clean that up for
>> your
>> >> > first
>> >> > > release.
>> >> >
>> >> >
>> >> > Jake mentioned the following:
>> >> >
>> >> > This is similar to other projects using a local third_party cache
>> >> directory
>> >> > > that have come to the Apache Incubator, Cassandra, Mesos and Aurora
>> >> are a
>> >> > > couple that jump into mind. We will ensure that this is addressed
>> and
>> >> > that
>> >> > > no source release contains any of these files.
>> >> >
>> >> >
>> >> > What do we need to do to address this? Do we have to remove them from
>> >> the
>> >> > repo and pull them at build time, or do we just need to check how we
>> go
>> >> > about including them in our distribution?
>> >> >
>> >> > We'd like to start whatever cleanup is required before we move the
>> code
>> >> to
>> >> > apache, so we can continue to cut releases while this is being
>> tackled.
>> >> >
>> >> > thanks,
>> >> > Bill
>> >> >
>> >>
>> >
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message