>>>>> "JN" == Jamie Nguyen <j...@jamielinux.com> writes:
JN> I couldn't find clear packaging policy on this. The guidelines [0] JN> talk about %config(noreplace) vs %config, but /etc/named.conf is JN> installed as a "noreplace" file. I don't think there's a guideline about this. %config and %config(noreplace) are simply flags that tell RPM what to do when the packaged version of a file differs from what's on disk and has no bearing on scriptlets. And note that the only guideline which could be meaningful is "don't modify config files in scriptlets", because RPM will simply overwrite the file on disk with what is in the package (perhaps keeping a backup) if the file isn't marked %config(noreplace). The only applicable guidelines are the general ones from the updates policy: Updates within a single Fedora version must not break user systems, and disruptive updates must be restricted to updates between distro versions. But always note that sometimes not breaking systems requires modifying a configuration file. - J< _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
