sample systemd service

[obbardc]

is it worth adding a sample systemd service into the repo ?

[brgl]

I did integrate this in meta-openembedded like so. This requires a service and two mount files. I'm not sure if it makes sense to include it here as it may differ from one distro to another. What are your thoughts as a debian person?

[obbardc]

I did integrate this in meta-openembedded like so. This requires a service and two mount files.

Thanks, if you don't choose to include the service files in this repo I think it'd make sense to have a link to these same service files in the README as it's a bit difficult to setup.

I looked at them, they look generic enough to be included in Debian or most other systemd OS in their current form.

I'm not sure if it makes sense to include it here as it may differ from one distro to another. What are your thoughts as a debian person?

Service files can go in downstream packaging, sure. BUT I guess that moves maintenance to the distro packager (which in the yocto world is fine, as it's you).

Like you say, if the service is different depending on the OS, then sure, it needs to be included in the recipe/package. BUT most of the time service files can be made generic enough surely ;-).

I don't really have a huge preference, but I'd prefer in most cases for upstream to include the service files, if they're generic enough then the packaging (or recipe) just installs the service files in the right place.

So TL;DR: I'd vote to move those service files in this repo and modify the yocto recipe to install them from upstream.

[brgl]

Sure, no objections. Do you want to send a PR? :)