Ah, I see now.
So we'll need votes for lib.profiler, dlight.nativeexecution, the
launchers and some other native libraries and utilities (CND has two or
three shared libraries/executables as well).
So why not build, deliver and vote all of these at once? That'd require
a single vote for all of them, right? Would that help?
Cheers,
Antonio
P.S.: Since these binaries have a different release cycle than the rest
of the code (I think we could compile them one/two three times a year,
right?) we could create a new repository "netbeans-binaries" to build
these (having the NetBeans repo as a submodule). There's no need to
build these on each one of the PR submits, right?
On 5/10/23 23:15, Neil C Smith wrote:
On Thu, 5 Oct 2023, 21:00 Antonio, <anto...@vieiro.net.invalid> wrote:
We currently depend on exechlp-1.2.zip [1] for dlight.nativeexecution,
right? But nobody has voted _explicitly_ on that dependency.
That's a pre-ASF binary as far as I know. However the ASF profiler binaries
should really have been voted on and hosted elsewhere.
We now build the new macos binaries for Apple Silicon, that we can
download from dist.apache.org and then include them as we do with
exechlp-1.2.zip.
And no extra voting is required, right?
They can't go on dist.a.o or Maven Central in the first place without a
vote (Windows launcher is on Maven incidentally via vote).
It is also distribution before release (even if only consumed by our
sources), and has some other potential issues. Some are raised on that
parent POM issue I linked. It has some parallels to this, although more
concern for us because these are compiled code.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
