runit-void: move os-release to base-files

[ahesford]

The os-release file really has nothing to do with runit and should be present even in the most basic installation, so it belongs in base-files. This also fixes some problems with meson calling Python's platform for host information in Void build containers (which don't install runit-void).

Testing the changes

• I tested the changes in this PR: briefly

[eli-schwartz]

This also fixes some problems with meson calling Python's platform for host information in Void build containers (which don't install runit-void).

The thing is that meson still doesn't read this file as far as I can tell, not even by the platform module, since the only function that attempts to read it is platform.freedesktop_os_release().

Not that it's a bad idea to move the os-release file, but I still don't understand how it's even possible to get a meson error here.

[classabbyamp]

the meson issue was a false alarm, I misread something, but i still think this is a good idea.

should /etc/hostname and /etc/locale.conf also be moved? those don't seem runit-related?

[ahesford]

should /etc/hostname and /etc/locale.conf also be moved? those don't seem runit-related?

That makes sense, so I made the change here.

[classabbyamp]

hm, the fact that those are conf files may cause issues. @Duncaen thoughts?

[ahesford]

Forcing a reinstallation to test the move caused my hostname file ti he inadvertently replaced, so there does seem to be risk here. If we can't avoid this, it may make sense to leave the conf files where they started.

[ahesford]

XBPS forgets about files marked as conf_files during the transition and will overwrite whatever is currently there. Abandoning the hostname and locale moves for now to avoid catastrophe.

Cf. void-linux/xbps#342 void-linux/xbps#426

[ahesford]

76f9490