Since this port records the version number of the system during the build, there is no way to update the version number stored in /usr/local/etc/os-release without rebuilding or updating the port. Therefore, the version number stored in the file becomes wrong as soon as the user updates the system with freebsd-update. Is it considered a problem, or it is just ignored?
I don't know what is the expected way to use the port, but it will be confusing to users if data stored in /usr/local/etc/os-release is used to show the version of the system. For example, gnome-control-center uses /etc/os-release to show OS version in its about page, and it is likely for a user to find the version number showed there is different from what freebsd-version command reports.
Yeah, that is not great. But as long as that is not part of the base system there is no easy fix for this, other than following the rule to upgrade ports after a system upgrade.
As that file is only needed to display some Operating System information in Qt and Gtk applications, a slight mismatch won't likely cause any problems other than confusion :)
(In reply to Tobias C. Berner from comment #1)
Instead of shipping an os-release file directly in the package, do you think it will be better if it ships a script which can be used to update the os-release file? It can also include necessary files to update it during boot in a way similar to motd or drop a file into /usr/local/etc/cron.d to check and update it every hour.
(In reply to Ting-Wei Lan from comment #2)
That sounds like a bit of overkill for what we use it for at the moment.
If stuff some day really requires it to be accurate, I think it should be shipped as part of the base system, and thereby be up to date through system upgrades.