Add Meson

[apprehensions]

For adding multiple distros as seen on dunst-project/dunst#1226

Personally, i do not understand the reason for such complicated build systems, if one can do something like Sway does: https://github.com/swaywm/sway/tree/master/.builds which is have only builds for alpine and arch, in a very simple CI manner.

[fwsmit]

This was discussed a bit already in dunst-project/dunst#1226 (comment). I do see value in having some more distro's in there. @bebehei do you have thoughts on this?

[bebehei]

The docker-images repository just exists to have pre-built docker images, which do not require package installation for every pipeline and just use the pre-assembled one.

At the end, this speeds up the overall build time.

Back in 2018 we also used Travis CI, which was horribly slow on top. So having a full repo, which runs the CI pipeline locally without the need to do a full checkin was also a huge benefit. Running the full pipeline on my own desktop machine was a matter of ca. 15 seconds.

I guess the swaywm buildsystem (IIRC it's sourcehut) has an optimisation for the package parameter, otherwise this will take a lot of time, too.

---

I agree, this might not be the best solution anymore. I also see, that it's a bit of an overkill, having 10 different DISTROS (not even different OSes like Linux/BSD etc.) in our CI. IMO we had enough cases justifying, that we test for different distros. There are common mistakes regarding differnt include paths, etc.

---

To add meson support, you just need to add the relevant meson packages into the Dockerfiles here:

https://github.com/dunst-project/docker-images/tree/master/ci

Afterwards the CI should pick up the changes easily (when #10 is implemented) and the dunst CI should use the images.