Create a 'nightly' branch with latest Unbound?

[churchofnoise]

Hi @klutchell ,

Before I started using Docker for Unbound, I'd often update Unbound to whatever the latest version of Unbound on Github was (call it 'beta' of so). To do so, I'd compile using what I pulled from Github with this command: git clone https://github.com/NLnetLabs/unbound.git . As you see, same command so no manual work in adjusting parameters.

Would you consider adding a parallel branch to this, similar to Pi-Hole's nightly branch, that updates automatically once a day, and provides the latest version as a parallel possibility to the 'latest' version? (fwiw, I run Pi-Hole's nightly docker image together with your Unbound image on today)

Just an idea of course!

[klutchell]

That sounds nice to have, but it's not quite as straight forward as cloning the unbound from the tip of master.

This project is compiled with buildroot, and uses the upstream recipe here: https://github.com/buildroot/buildroot/blob/master/package/unbound/unbound.mk

Whenever there is a new unbound release I patch upstream buildroot master, and the buildroot LTS used by this project. Then I add the patch file to the root of this repo like in #103.

So to track unbound nightly, we would need to...

1. adjust the buildroot unbound recipe to clone unbound master instead of fetching from https://nlnetlabs.nl/downloads
2. the above recipe would also have to ignore the sha validation and just trust the tip of master (if buildroot allows this)
3. create a patch with the modified recipe above
4. optionally apply this patch to build a nightly version of this project

So I think it can be done, with a few unknowns, but not as simple as if I were not using buildroot.

I will keep this issue open in case I find the time, or someone else wants to tackle it, cause it's a good idea!