Integrate the Solution
In this guide, you'll learn about the different ways you can integrate the eyeo Browser Ad-Filtering Solution into your own Chromium-based browser project.
Integration strategies
You can integrate eyeo's changes into your own Chromium project in three ways:
Strategy 1: Base your product on top of eyeo's changes
Strategy 2: Download modules and apply them to your source code
Strategy 3: Create a patch with changes and apply it to your source code
Strategy 4: Copy eyeo's functionality into your adapation
In the following sections, you'll learn the advantages of each strategy.
eyeo recommends Strategy 1.
About automation
If you decide to automate the steps to copy eyeo's functionality into your adaptation, remember to:
Write the script files that automate the steps.
Update the scripts when branch/tag naming agreements are changed or the release flow is changed.
As with any automated, consider whether the time saved will compensate for the efforts to write and test the automation scripts. eyeo can help you decide, so reach out to us with any questions.
eyeo's versioning scheme
For an example Chromium release tag of 113.0.5672.76
, eyeo's release tag would be eyeo-release-113.0.5672.76-v1.diff
. This tag would contain all Solution-related changes, based on top of the corresponding Chromium release.
Because eyeo hosts the Browser Ad-Filtering Solution in remote Git repositories, you can find the Solution release for each version:
Usually, one release tag is available for each major Chromium version. Patch releases may also be available if eyeo finds a critical bug in the release.
Last updated