Re: Switching package to fragmented default configuration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

On Mon, 2020-08-31 at 23:46 -0700, John M. Harris Jr wrote:
> On Monday, August 31, 2020 11:24:57 PM MST David Tardon wrote:
> > On Mon, 2020-08-31 at 00:08 -0700, John M. Harris Jr wrote:
> > 
> > > On Saturday, August 29, 2020 3:36:33 PM MST Colin Walters wrote:
> > > 
> > > > https://blog.verbum.org/2020/08/22/immutable-%E2%86%92-reprovisionable-a
> > > > nti-> 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.
> > 
> > The problem with this way is that it is simple, but *not* robust.
> > That's why I have to look for .rpmnew files after every update.
> 
> That's to be expected. 

Expected by whom? I for one don't see why I should have to manually
merge configuration changes to the end of times just because I have
changed a single option. I'd rather waste my time in other ways.

> The package manager shouldn't destroy your config when 
> the package has a different one, and it doesn't. 

It wouldn't have to care about my modifications if I could do them
separately from the distro-installed configuration file... IOW,
fragmented configuration allows me to do my own small modifications
while following the upstream/distro configuration changes. Which is
exactly the thing I want most of the time. It's a pity many projects
don't support it (yet).

> You don't need to look for 
> them though, just look at the output from `dnf` during the update.

Gee, thank you very much for your advice... I'll certainly do just that
when I'll be upgrading my machines to F-33... But for the time being
I'll stick to running "git status" in /etc .-)

D.
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux