>>>>> On Tue, 27 Mar 2007 22:26:05 -0700, >>>>> "TK" == Toshio Kuratomi <a.badger@xxxxxxxxx> wrote: TK> 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 Yes, something like that. TK> If the font is removed, then the config file has to be updated. But the TK> thing is that the user intiates all of these actions. We don't remove TK> the package from the user's system. The user has to decide : Well, as you may know, fonts-japanese collects various Japanese fonts and I presume that the font file is removed from the package without adding/removing any packages. and it also provides configuration files for ghostscript to be able to print japanese text out correctly, which we are talking about now. TK> If the user doesn't change the config file and the next package TK> iteration has a different configuration in the file, the file will be TK> replaced despite it being %config(noreplace). %config() macros only TK> kick in when the file has been modified on the installed system. Right. I'm worrying about they may add another line to it or modify it partially etc, which is still referring to the old fonts. Another idea to solve this is, to makes it read-only file and to create the empty configuration file for users, which can overrides the sytem's. -- Akira TAGOH
Attachment:
pgpETqLPYicDe.pgp
Description: PGP signature
-- 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
