Packaging

Table of Contents

• For Distribution Packagers
  • Ozone-Wayland release
  • FAQ

# For Distribution Packagers

Ozone-Wayland project doesn't intend to constantly build releases of Chromium Wayland Browser. Instead, we believe it is easier for distributions maintain their own build of Chromium Wayland, based on their toolchain and package its build. Ozone-Wayland is committed though to make the life easier of all serious Linux distributions that want to create these packages.

## Ozone-Wayland release

Check here

## FAQ

• Chromium project releases a new Chromium stable release for Linux, let's say 32.0.1234.56. I, as a packager, use the release branch and prepare to package it for my distro. What other steps do I need to add to my workflow to have Wayland support?

Required steps: Let's assume the working directory as chromium-release.

1. Download right Ozone-Wayland release from here(Ensure the version no is same).
2. Unzip Ozone-Wayland and copy files to chromium-release/src.
3. cd ~/chromium-release and run ./src/ozone/patches/patch-chromium.sh
4. export GYP_DEFINES='use_ash=0 use_aura=1 chromeos=0 use_ozone=1'
5. cd src
6. ./build/gyp_chromium
7. ninja -C out/Release -j16 chrome

• Chromium project releases a new Chromium stable release for Linux, let's say 32.0.1234.56. I, as a packager, download it and prepare to package it for my distro. What other steps do I need to add to my workflow to have Wayland support? TODO