[PATCH] Generate os-release from component parts

[Peter Robinson]

> Dennis, can you get me some specific examples I can look at and account for? Also see below for why this may not be an issue.
>
>
>> I
>> think that systemd itself needs /usr/lib/os-release and/or /etc/os-release to
>> be present to actually boot the system.
>>
>
> Zbigniew, is this accurate? Does systemd need this file on the disk to boot?
>
> In any case, I think this may not be an issue in the current approach, as I'm generating the file at package install time as well at each boot, so the previous boot's os-release file will be there.
>
> I do need to change %post to call the script directly instead of using the service, though. Otherwise that will fail during anaconda.
>
>
>
>> perhaps we should take the approach that we put /usr/lib/os-release in place
>> and make the /etc/os-release symlink, we have the service provided in fedora-
>> release but disabled. the preset files for the products enable the service and
>> it replaces the symlink at /etc/os-release with a new file that includes the
>> base os definition and the variant definition.

What about having the /usr/lib/os-release one as static without
product info (as anything in /usr/lib should static and never change
anyway and then write out one to /etc/os-release for product stuff
(where stuff is allowed to change). That way there will be always a
generic distro one to fall back to and it shouldn't affect the boot
process, and then have the generated one based on product can change
as necessary?

Peter