Very true! Thanks, Neil.
So, to summarize:
- Option 3:
Make cnd depend on cpplite (heavy depends on lite, as Neil suggests).
- Option 4:
Bring cpplite and cnd together under the cnd cluster.
The question is then
A) if we want to have separate "lite" and "heavy" C/C++ support, with
different NetBeans binaries targetted for different Java and Lite vs.
Heavy C/C++ oriented audiencies (cost being more complexity in handling
binaries). Then Option 3 seems the way to go.
B) if we want to bundle everything together, with a single binary for
all audiences (cost being longer builds). Then option 4 seems the way to go.
I think I like B (Option 4) better than A (different NetBeans binaries).
Opinions?
Thanks,
Antonio
El 8/1/22 a las 15:17, Neil C Smith escribió:
On Sat, 8 Jan 2022 at 14:04, antonio <[email protected]> wrote:
Option 3:
Make "cnd.editor" depend on "cpplite.editor". This will make the cnd
cluster depend on the cpplite cluster.
So, what say? Any preferences? Any alternatives?
You seem to have missed the option you mention in the PR of combining
them? If they remain separate, what are their distinct purposes in
future? If you consider as lite and "heavy", or basic and advanced,
then cnd depending on cpplite makes logical sense?
Best wishes,
Neil
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
