#423 Added PKG Installer build for macOS systems#2098
Open
laim2003 wants to merge 11 commits into
Open
Conversation
laim2003
added
install
Collaborator
Coverage Report for CI Build 28707177014Coverage increased (+0.004%) to 71.836%Details
Uncovered ChangesNo uncovered changes found. Coverage RegressionsNo coverage regressions found. Coverage Stats
💛 - Coveralls |
laim2003
changed the title
laim2003
changed the title
…staller debugging screen
laim2003
force-pushed
the
feature/#433-macos-installer
branch
from
4a6b166 to
51a5cc9
Compare
Contributor
|
@laim2003 
|
Contributor
Author
|
@oanding-blrng Can you maybe upload the information that is printed to the installation protocol? So the content from „Fenster“->“Installationsprotokoll“; here in the logs there either is an error, or a log message printing the path to the (second) IDEasy internal installation log. Could you maybe upload both so I can investigate what exactly goes wrong on your device? I suspect that this may not actually be a gatekeeper issue, but I'm not sure. Thanks!
… Am 06.07.2026 um 11:36 schrieb OAnding ***@***.***>:
oanding-blrng
left a comment
(devonfw/IDEasy#2098)
<#2098 (comment)>
@laim2003 <https://github.com/laim2003>
I'm able to create the PKG installer, but I can't install IDEasy with it. It get the following output from the installer which is fine due to the mentioned lack of the Apple Developer License. But the mac gatekeeper workaround isn't working for me, because the option to allow the specific program doesn't appear. The workaround still works for the traditional way via extracting the .tar.gz and running setup.
Bild.06.07.26.um.10.44.png (view on web) <https://github.com/user-attachments/assets/ec068ead-7c7e-404b-a549-3a929ca3c4cb>
—
Reply to this email directly, view it on GitHub <#2098?email_source=notifications&email_token=AJQDEFQP5A4BWPR5MAV4DS35DNXKRA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBZGEZDMNJZHAZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4891265983>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJQDEFWAV7DHJORFWMPYGZL5DNXKRAVCNFSNUABFKJSXA33TNF2G64TZHM3DSMRQG43DINRUHNEXG43VMU5TINZYGQZDMMBUHAZKC5QC>.
You are receiving this because you were mentioned.
|
|
Installation protocol (Error and status messages): Last message mentioned a problem with the UI. Maybe the underlying problem here is connected to the nightly build (https://github.com/devonfw/IDEasy/actions/runs/28696754044/job/85107587327). |
Contributor
Author
|
@oanding-blrng i quickly pushed a small fix. now, when you look at the installation log, you should see a log message that points to the IDEasy installation log. Also, what size did the installer display when choosing the disk? |
|
The installtion log: The installer is showing 62,5 MB for the size. Although not in the "Choose Disk" but rather in "Installation type". I only have one big partition for the hard drive. I assume, that MacOS and the installer dosn't bother to ask if there is only one possible option to choose. |
|
For better manual testing I extracted the relevant commands from the jobs of release.yaml into it's own script. maven_config="$(cat .mvn/maven.config)"
current_version="${maven_config/#*-Drevision=}"
current_version="${current_version/ */}"
next_version="${current_version/-SNAPSHOT/}"
cd cli
mvn -B -ntp -Drevision=${next_version} -Pnative -DskipTests=true package
cd ..
cd documentation
mvn -B -ntp clean install
cd ..
mkdir -p macos-installer/pkg-root/Library/IDEasy/bin
mkdir -p macos-installer/Resources
cp documentation/target/generated-docs/LICENSE.rtf macos-installer/Resources/LICENSE.rtf
cp -r cli/target/package/* macos-installer/pkg-root/Library/IDEasy/
rm -rf macos-installer/pkg-root/Library/IDEasy/system/windows
rm -rf macos-installer/pkg-root/Library/IDEasy/system/linux
cp cli/target/ideasy macos-installer/pkg-root/Library/IDEasy/bin/
chmod +x macos-installer/pkg-root/Library/IDEasy/bin/ideasy
chmod +x macos-installer/scripts/postinstall
cd macos-installer
pkgbuild --root pkg-root --identifier com.devonfw.ideasy \
--version $next_version --install-location "/" \
--scripts scripts IDEasyComponent.pkg
sed -i '' "s/\${next_version}/${next_version}/" Distribution.xml
productbuild --distribution Distribution.xml --resources Resources \
--package-path . IDEasy-$next_version.pkg |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes #423
Implemented changes:
A few notes:
Testing instructions
Disclaimer: Testing this requires a mac.
Build native imageand thenBuild MacOS PKG) and running them from /workspaces/main/ideasy/idecommand should be usable from the command line.Retesting:
Checklist for this PR
Make sure everything is checked before merging this PR. For further info please also see
our DoD.
mvn clean testlocally all tests pass and build is successful#«issue-id»: «brief summary»(e.g.#921: fixed setup.bat). If no issue ID exists, title only.In Progressand assigned to you or there is no issue (might happen for very small PRs)with
internal