Sounds great and thanks for doing this. Gj
On Wed, 18 Oct 2017 at 20:26, Jan Lahoda <lah...@gmail.com> wrote: > On Tue, Oct 17, 2017 at 10:06 PM, Antonio Vieiro <anto...@vieiro.net> > wrote: > > > > > > El 17 oct 2017, a las 21:42, Jan Lahoda <lah...@gmail.com> escribió: > > > > > > Hi Antonio, > > > > > > On Sun, Oct 8, 2017 at 12:36 PM, Antonio Vieiro <anto...@vieiro.net> > > wrote: > > > > > >> I understand, thanks for the info. > > >> > > >> I think that once we have maven group/artifact/version coordinates for > > >> each of the files in binaries_list we could try to automatically > > generate > > >> notice files (as in [1]). > > >> > > >> I’ll take a look at how this can be automated. > > >> > > > > > > Did you have a chance to look at this? I think it would be good to > start > > > looking at producing the appropriate LICENSE/NOTICE(/DEPENDENCIES) > files > > > for distributions we do, should I look at that, or is that part of what > > you > > > want to look at? > > > > > > > Hi Jan, > > > > This is a bad week for me (helping out a customer with a big mess) so I > > won’t be able to look at this at all. Your lead here would be most > > appreciated. > > > > Ok. I am peeking at this. Unless there are objections or better ideas, I'll > create a new branch for this over the next few days, and a (platform) build > to produce the zips, so that the content of all the files can be checked. > > Jan > > > > As time permits I’d like to tackle the generation of binaries for those > > modules that have patches to third party source code, and that cannot be > > then downloaded from Maven. > > > > Un abrazo, > > Antonio > > > > > > > > >
