fonts packages review and conffile-without-noreplace-flag warning

Toshio Kuratomi a.badger at gmail.com
Wed Mar 28 05:26:05 UTC 2007


On Wed, 2007-03-28 at 13:35 +0900, Mamoru Tasaka wrote:
> Tom "spot" Callaway wrote:
> > On Wed, 2007-03-28 at 11:25 +0900, Akira TAGOH wrote:
> >>>>>>> On Tue, 27 Mar 2007 09:12:41 -0500,
> >>>>>>> "TC" == "Tom \"spot\" Callaway" <tcallawa at redhat.com> wrote:
> >> TC> Question: Is it really a configuration file?
> >>
> >> TC> To determine this, ask, will a user be permitted to change it? If the
> >> TC> answer is yes, then the user will be quite unhappy to have it replaced
> >> TC> by the stock copy when they do a package update. If it is not something
> >> TC> designed to be hand-edited (or shipped with a tool to edit), then its
> >> TC> probably not a config file.
> >>
> >> Yes, it's a configuration file that designed to determine
> >> the connection between PostScript fontname and the real
> >> font. someone may wants to use another one rather than the
> >> default font. those would be helpful in this case.
> >>
> >> However my question is, what happens if the default font is
> >> changed? 
> > 
> > I would say that if they changed it to use a specific font, then, they
> > really want that specific font, whether the default changes or not.
> 
> Here Akira says is perhaps.. what happens if the previous fonts is
> completely _removed_ (due to license issue or something)?
> In this case, user-customized config file completely gets useless.
> Well, this actually happened on fonts-japanese
> 
If the font is removed, then the config file has to be updated.  But the
thing is that the user intiates all of these actions.  We don't remove
the package from the user's system.  The user has to decide :

1) I want to override the default font.  Make changes
to /etc/configfontfile.
2) Oops.  I don't like that font anymore.  I'm going to rpm -e foo-font
3) Okay.  I need to change the configfontfile so it points to a font
that I still have installed.

If the user doesn't perform actions 1 or 2 then action 3 is not
necessary.

> I hear some peole say, "well, actually the configuration will
> change in the future, so I want to leave this configuration file
> as not noreplace".
> 
If the user doesn't change the config file and the next package
iteration has a different configuration in the file, the file will be
replaced despite it being %config(noreplace).  %config() macros only
kick in when the file has been modified on the installed system.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-maintainers/attachments/20070327/b128d20b/attachment.sig>


More information about the Fedora-maintainers mailing list