[Bug 511668] FTBFS knm_new-fonts-1.1-5.fc11

[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.


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





--- Comment #11 from Akira TAGOH <tagoh at redhat.com>  2009-07-21 03:56:28 EDT ---
(In reply to comment #9)
> Well, fontpackages used to do no processing on the name the packager gave to 
> %_font_pkg and many packagers got it wrong, resulting in lots of back and forth
> getting them to fix it. So now it massages the name given in argument to try to
> correct it. It fixes many human problems and improves packager poductivity.

That's really nice feature though.

> I *really* do not want to add any more package naming processing to
> fontpackages. It is already quite over-engineered without needing to handle a
> fixed list of historical exceptions to guidelines. Given that this is the
> *only* font package that fails because of an underline, would it be possible to
> rename it to use the standard fedora package name separator ?
> 
> I'm quite sure the guidelines exception list was written to avoid unnecessary
> work on existing packages, but trying to maintain it will have the reverse
> effect now.  

We've missed upstream contact already as upstream URL has been commented out in
the spec. no way of telling them to rename the font name either. "knm_new" is
really upstream name and it should matches to the exception reason but just not
to avoid the unnecessary work on existing packages.

(In reply to comment #10)
> BTW looking at the font files they declare a generic name (Fixed) which seems
> not quite right to me. It will collide with other packages  

Sure. it was supposed to work an alternative of better "Fixed" font for
Japanese support though.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.