Toshio Kuratomi wrote: > 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@xxxxxxxxxx> 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. No, for fonts-japanese, the package actually removed (and had to remove) one fonts. There is no font named "fonts-japanese". This is a correction of about 10? different fonts and config file points to one font by default. What happened to fonts-japanese is that this font used as default (which was very common) had to remove completely due to license issue. So simply upgrading fonts-japanese actually removed one font. At this point, user-customized config file became quite useless. And many changes happened according to this default font change, along with ghostscript change (yes, this was really many). > 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.e. we *had to* do 2) despite what a user may think. Mamoru -- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers -- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
