New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/issues/54043#issuecomment-2849171643

Comment:
This is an imaginary issue.

In general, any service can have an arbitrary list of seemingly trivial prerequisites. It is not the job to ensure that all are met. Ultimately, the user is responsible for understanding and satisfying these prerequisites. This is especially true when the user breaks customary expectations like the availability of persistent storage for logs. If you're going to mount something ephemeral over directory structures created by the system, you should take steps to ensure that the hierarchy below is recreated at the time of mount, whether or not consumers of that directory deign to make a good-faith effort to repopulate the hierarchy on demand.

We will certainly consider PRs that increase user convenience by creating an expected directory on demand or even allowing the user to configure the location of expected directories. However, these proposals must stand on their own utility. The existence of footguns in Void is not a problem *ipso facto*.