%tmpfiles_file and %sysusers_file macros

[ReillyBrogan]

The %tmpfiles macro doesn't really seem as ergonomic as being able to have the contents of the tmpfile in a separate file entirely. Perhaps we could have the %tmpfiles_file and %sysusers_file which take a path instead (and otherwise do the current append behavior of the current macros)?

[sunnyflunk]

The design is for the stone.yml to include as much of the build as possible within reason (and why there won't be a separate patches file). The macro is the preferred and best option to do that.

One line in the stone.yml vs one line in a separate file and the former is always better.

[sunnyflunk]

If the file approach is preferred, then there are a few requirements (I don't think we will bother having both):

• Check that the file already exists (we don't want to clobber an upstream file). If the upstream definition is insufficient it should be patched.
• Default to the name of the package. In most circumstances it is the correct filename.
• Standardise the inclusion. i.e. %(pkgdir)/%{name}.tmpfiles as the file and %tmpfilesd will install it to the right place
• Allow for overriding the name in extreme circumstances (should be pretty rare). %tmpfilesd ${NEWNAME}