[Bug 514549] Review Request: lyx-fonts - Math Symbol fonts

[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=514549





--- Comment #5 from Jussi Lehtola <jussi.lehtola at iki.fi>  2009-07-30 02:22:59 EDT ---
(In reply to comment #4)
> (In reply to comment #3)
> > Is it really worth it?
> 
> Please don't shoot at people that do much needed cleanups at apply our own
> official packaging guidelines

I was not shooting at people.

I was just discussing whether having an own spec file for a bunch of stuff
taken from the tarball is worth it, since usually that is frowned upon. I did
*NOT* criticize font packages or the cleanup. Please don't make such hasty
accusations.

One should be able to concatenate this spec file to that of lyx and still
respect the font packaging guidelines.

If the font packaging spec file macros don't work for this purpose (which IMHO
they should to avoid duplicating unnecessary package maintenance work), then
there is a solid reason for having this second spec file for the same tarball.
Note that the Font Packaging Guidelines _do not_ have a specific policy on this
case.

> > For comparison, lyx-1.6.3-1.fc11.i586.rpm is 11M. And if nothing changes in the
> > contents of the fonts packages, the delta RPMs are almost nonexisting. 
> 
> fonts are not being split for volume reasons but multiple others that were
> detailed to FPC when the guidelines were written: technical requirement for the
> font autoinstall logic to work, explicit legal audit of each font, etc.
> 
> If you disagree make your case before FPC and have the guidelines changed but
> do not complain at people who apply them.  

I was not asking about this. I was asking whether it's really worth it having a
spec for both lyx and lyx-fonts which both operate on the same lyx tarball.

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