On Saturday, August 29, 2020 3:36:33 PM MST Colin Walters wrote: > On Sat, Aug 29, 2020, at 2:19 PM, Igor Raits wrote: > > > > And only way to get to the distribution defaults is to download RPM > > with matching version, unpack it and get its /etc/foo.conf. > > > On ostree-based systems, the defaults for /etc are in /usr/etc, so > you always have them - it needs this to do the "3 way merge" upgrade > for config files. > > > > > What is the actual benefit of this? Needlessly breaking existing > > > configuration, making it impossible to cleanly upgrade systems, > > > or write logic that takes into account the existing configuration of > > > a given > > > program? If you blow away /etc/, you will have a well and truly > > > broken system. > > > If you want to start a configuration from scratch, re-install. > > > There's nothing > > > wrong with that approach, and it works very well. This has been the > > > case for > > > nearly three decades now > > > https://blog.verbum.org/2020/08/22/immutable-%E2%86%92-reprovisionable-anti-> hysteresis/ > touches on some of the benefits of "fragmented" configs. Perhaps this should be done for the ostree-based systems, so it doesn't much up the ones people use commonly. Have the hip new way along the side, while doing things the simple, robust way elsewhere. This way, everyone benefits. Sysadmins don't have to deal with that nightmare, packagers don't have to deal with it, upstream software devs don't get patches flying in from all around to apply this to their software, and folks that want to give it a go can play around with the idea in a sandbox environment with little ramifications if it changes. -- John M. Harris, Jr. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx