Hi Jan, On Mon, Mar 5, 2018 at 3:29 PM, Jan Lahoda <[email protected]> wrote: > ...Originally, the binaries of the launchers where simply committed in the > repository (because there is just a handful of them, and their source is in > the repository): > http://hg.netbeans.org/jet-main/file/tip/o.n.bootstrap/launcher/windows > > But in Apache, built stuff can't be in the source release, so these are > downloaded from the binary server: > https://github.com/apache/incubator-netbeans/blob/master/o.n.bootstrap/external/binaries-list > https://github.com/apache/incubator-netbeans/blob/master/o.n.bootstrap/external/platform-launchers-8.2-license.txt > ...
Ok, got it, so you have a "magic" platform-launchers-8.2.zip which has launcher binaries that are incorporated into the build by downloading them at build time. That's similar to how many builds use Maven repositories, and in Maven's case people have the option of configuring their own Maven repository and strictly controlling what goes into that. I think a similar setup would be best - if you have a single place where people can configure their alternate repository for binaries before building, and there's information about that in the README that's reasonable. And people who don't care can get the magic binaries from wherever, and the digests used by the NetBeans build at least guarantee that everybody gets that same binaries, right? -Bertrand --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
