[jggimi]

@dnix, if you've tried this third party service already, I hope you had success.

I'd like patches whenever available, but don't want to do them by hand and/or rebuild everything.

Please consider adding both of these skills to your repertoire. OpenBSD is not just source-code maintained, it is source-code supported.

Should you ever have a problem requiring support, the developer(s) supporting you will only send you a source-code patch for testing. Their patches will not go into -stable until you have confirmed the patch resolves your problem and creates no new ones. Developers will neither replicate your environment nor test the patch for you. They won't build kernels or other binary modules for you either; they might not even have access to the same hardware architecture you use.

Errata patches will give you a feel for what it takes to implement a single patch "by hand" if needed. These are published on the web and always include instructions. There is usually very little actually done by hand for most patches. As an example, the most recent errata patch was published in February, for the 4.8 kernel, and included the following instructions:

Apply by doing:
    /usr/src
    patch -p0 < 010_sis.patch

Then build and install a new kernel

Kernel patches require kernel builds, which is a fairly automated process, described in both the Following -stable FAQ as well as FAQ 5.3.4. Userland patches carry complete step-by-step instructions, such as this 4.8 example:

Apply by doing:
    cd /usr/src
    patch -p0 < 001_bgpd.patch

Rebuild and install the bgp daemon:
    cd usr.sbin/bgpd
    make obj
    make depend
    make
    make install

Patches are always submitted, published, and shared using a standard format called "unified diff". This format is easy to read and understand, even when you are not a programmer. You may not understand the specifics of the change, but you can see what was added, deleted, or altered in context.

If you have missed the Following -stable FAQ you may find it helpful for understanding what it takes to maintain your own -stable system(s).