macOS (PKG) Installer Creation

[vikman90]

Parent Issue:

• Create Installation Packages for Wazuh Agent #128

Description

This issue involves creating a PKG installer for macOS to enable easy installation of the Wazuh agent. The installer should set up the agent as a launch daemon, configure necessary permissions, and handle post-installation tasks.

Functional Requirements

• Develop a PKG installer for the Wazuh agent on macOS 14+.
• Ensure the installer sets up the Wazuh agent as a launch daemon.
• Handle file permissions, configuration files, and any required installation scripts.

Acceptance Criteria

• The PKG installer successfully installs the Wazuh agent on macOS.
• The Wazuh agent is configured as a launch daemon and starts automatically after installation.
• The installation, uninstallation, and upgrade processes are tested and verified on macOS 14+.

[mjcr99]

Update:

(13/11/2024) Updated code to bring last changes from wazuh/wazuh, working on changing the build process and adding new files.
(14/11/2024) Adapting the mac OS generation script to handle binary caching and cover derivated dependencies.
(15/11/2024) Currently working on modifications for the install process in mac OS. Having problems with Cmake and installing the built agent in / direcotories. Moved to on hold.
(21/11/2024) Updated scripts to deal with package building dependencies.
(27/11/2024) Resumed work, updated Cmakelist.txt to deal with Mac OS and Linux Service files.
(28/11/2024) Packages are able to be built, still pending solve some problems regarding installation path since we following log appearing when trying to install:

vagrant@idr-1819-sonoma-14 macos % sudo installer -pkg output/wazuh-agent_5.0.0-1_intel64_ab34bf38d.pkg -target /
installer: Package name is wazuh-agent_5.0.0-1_intel64_ab34bf38d
installer: Installing at base path /
installer: The install failed. (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. The package is attempting to install content to the system volume.)

(29/11/2024) Regarding the problem related to the installation path some research have been done.
The following packages have been downloaded and inspected to understand their structure:

vagrant@idr-1819-sonoma-14 ~ % ls -l pkg_files                                                                               
total 1605104
-rw-r--r--  1 vagrant  staff  370007450 29 nov 02:15 MonoFramework-MDK-6.12.0.206.macos10.xamarin.universal.pkg
-rw-r--r--  1 vagrant  staff  113838696 29 nov 01:54 Slack-4.41.98-macOS.pkg
-rw-r--r--  1 vagrant  staff  131198478 29 nov 02:43 VirtualBox.pkg
-rw-r--r--  1 vagrant  staff  199901970 29 nov 02:01 googlechrome.pkg
-rw-r--r--  1 vagrant  staff    6856848 29 nov 01:56 wazuh-agent-4.9.2-1.intel64.pkg

All external packages except Mono use a scaffolding where the package's files are installed in the root directory, in a folder with the name <program_name>.app, for example, for the case of Google Chrome we see: ./Google Chrome.app/.

Under this main folder, it has been observed, there is a unique folder named Contents, and under it, there are different folders such as Library, Frameworks, and Resources. We should consider using this type of package structure since it seems to be the most widely used.

Some other packages, that have been downloaded as .dmg files (disc images) can be mounted and also present this kind of structure. Refer to this documentation page for more information.
(02/12/2024) Opened final PR with proposed solution:

• Let the macOS package be built #376

(05/12/2024) Updated script options to better manage different phases of the package building procedure.