[Bug 178922] Review Request: asterisk - The Open Source PBX
bugzilla at redhat.com
bugzilla at redhat.com
Thu Jan 26 15:15:03 UTC 2006
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: asterisk - The Open Source PBX
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178922
------- Additional Comments From che666 at gmail.com 2006-01-26 10:14 EST -------
> lets assume we go ahead various versions of asterisk... and how high do you
> eval the chance the the old config will be broken in newer releases? in my
eyes
> if they werent changed by the user they should really be replaced by the new
> versions default configs. i am not sure if theres a policy regarding that or
> not.
%config(noreplace) does not mean that unedited config files will not be replaced
- they will. The difference in behaviour between %config and %config(noreplace)
comes in when the user has edited the config file. With %config, the user's
edited file will be renamed to file.rpmsave and the new package's config file
will take its place. With %config(noreplace), the user's edited file will be
left alone and the new package's file will be installed as file.rpmnew.
%config(noreplace) should generally be used for config files unless there's a
good reason not to use (noreplace).
well(In reply to comment #9)
> (In reply to comment #8)
> > lets assume we go ahead various versions of asterisk... and how high do you
> > eval the chance the the old config will be broken in newer releases? in my
eyes
> > if they werent changed by the user they should really be replaced by the
new
> > versions default configs. i am not sure if theres a policy regarding that
or
> > not.
> %config(noreplace) does not mean that unedited config files will not be
replaced
> - they will. The difference in behaviour between %config and %config
(noreplace)
> comes in when the user has edited the config file. With %config, the user's
> edited file will be renamed to file.rpmsave and the new package's config file
> will take its place. With %config(noreplace), the user's edited file will be
> left alone and the new package's file will be installed as file.rpmnew.
> %config(noreplace) should generally be used for config files unless there's a
> good reason not to use (noreplace).
if thats the behaviour i am pretty fine with it.
p.s. back then when i last looked at it i couldnt find proper documentation
about %config really. thanks for clearing that.
--
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the fedora-extras-list
mailing list