[Bug 225765] Merge Review: fonts-japanese

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Merge Review: fonts-japanese


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=225765





------- Additional Comments From tagoh at redhat.com  2007-03-26 08:41 EST -------
(In reply to comment #9)
> The new build still have rpmlint problems.
> 
> W: fonts-japanese rpm-buildroot-usage %build %configure --disable-bold
> --disable-italic --with-fontdir=$RPM_BUILD_ROOT%{bmpfontdir}
> $RPM_BUILD_ROOT should not be touched during %build or %prep stage, as it
> will break short circuiting.

As I've mentioned at comment #3, I'm sure it won't breaks anything.

> W: fonts-japanese conffile-without-noreplace-flag /etc/ghostscript/CIDFnmap.ja
> A configuration file is stored in your package without the noreplace flag.
> A way to resolve this is to put the following in your SPEC file:
> 
> %config(noreplace) /etc/your_config_file_here

Do we really want to add noreplace flag to %config whatever happens?
I think I have explained about those files on IRC or somewhere though, those
files are written in PostScript actually. I understand it may be annoyed when
every upgrading happens but if updating is necessary for any serious reasons,
such as imcompatible or buggy code etc (not saying about it will happens, but
just may be likely), or things most likely to happen would be to change the
default font. how do we take care of that in general? just inform that on the
mailing list or so and change that manually?
We should prevent to happen that, but it may be hard to not happen that accident
at all. I'm just curious how to deal with that, because it will becomes not
working properly then.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.