More or less nothing, I was just being overly finicky about it. My fork
turns out to be based on your old f23a61e commit (2 Aug 2018), so yours
has changed considerably more than mine since then. The only obvious
functional difference I spot in the update are:
*install.sh*
- Updated application name to be unversioned (as current release)
- Updated link to binary to use "/netbeans/" instead of
"/NetBeans/" (for unlikely case-sensitive FS scenario)
*Info.plist
* - Updated CFBundleName/CFBundleDisplayName to be unversioned (as
current release)
- Updated CFBundleIdentifier to same as release (prevent multiple
NB instances changing same config?)
- Updated CFBundleSignature to same as release (no idea if this
makes any difference; guessing not)
- Removed
CFBundleDocumentTypes/NSHighResolutionCapable/NSSupportsAutomaticGraphicsSwitching
My primary thinking was just to ensure multiple similar versions
wouldn't accidentally be running, to avoid configuration directory
clashes. The removal of the 3 Info.plist keys seems fairly trivial, and
I'm imagining the last two are by default set now anyway. I imagine your
current script works fine as it is.
Stan
On 23/05/2025 12:51, Carl Mosca wrote:
Ah, not look at that script in a good bit Stan. Now you have me curious
about what tweaks were needed.
Carl
On Fri, May 23, 2025 at 7:28 AM Giles Winstanley<s...@snaq.net> wrote:
The potential for it to be marked as broken was something I had in mind,
but curiously it seems to have worked fine. And "doing all that" amounts
to essentially two/three terminal commands, so little lost if it turns
out not to work down the line. In case anyone else wants to try:
# Remove bundled JDK & compiled launcher
cd "/Applications/Apache NetBeans.app/Contents" && sudo rm -rf Home
MacOS/netbeans
# Create link to script-based launcher
sudo ln -s ../Resources/netbeans/bin/netbeans MacOS/
I'll stick with trying this version for now, as at least it should have
the various binaries signed. As it happens I found I've also still got
my old fork of Carl Mosca's netbeans-macos-bundle script lying around,
which seems to have successfully bundled it from the binary zip with a
couple of small tweaks, so if the above doesn't work I'll try that instead.
For now at least...problem solved.
Stan
On 22/05/2025 16:46, Neil C Smith wrote:
On Thu, 22 May 2025 at 16:42, Giles Winstanley<s...@snaq.net> wrote:
Fair enough; turns out after a quick test it should be fine to delete
the Home directory & netbeans binary within the bundle, then create a
symbolic link to the usual netbeans script, as older scripts used to do.
I'm half expecting some permissions issues to pop up, but hopefully this
will work out.
This will probably lead to the app being marked broken.
If you've doing all that, just use the zip instead.
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
---------------------------------------------------------------------
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
