From Fedora Project Wiki
(New page: <noinclude>{{CompactHeader|fonts-sig}} Since fonts have specific packaging and legal requirements, but are often hidden deep into other stuff, make sure the packager checked for their exi...) |
m (PackagingDrafts/ReviewGuideline for fonts (2009-01-22) moved to Archive:PackagingDrafts/ReviewGuideline for fonts (2009-01-22): wiki cleanup) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
Since fonts have specific packaging and legal requirements, but are often hidden deep into other stuff, make sure the packager checked for their existence (to avoid needing a new painful audit in a few releases). | Since fonts have specific packaging and legal requirements, but are often hidden deep into other stuff, make sure the packager checked for their existence (to avoid needing a new painful audit in a few releases). | ||
== The change == | |||
Add the following line to [[Packaging/ReviewGuidelines]]: | Add the following line to [[Packaging/ReviewGuidelines]]: | ||
</noinclude> | </noinclude> | ||
* '''MUST''': Font files<ref>''.otf'', ''.ttf'', ''.ttc'', ''.pfa'', ''.pfb'', ''.pfc'' files.</ref> pass [[Legal_considerations_for_fonts|legal checks]] and are packaged according to [[Packaging:FontsPolicy]]. | * '''MUST''': Font files<ref>''.otf'', ''.ttf'', ''.ttc'', ''.pfa'', ''.pfb'', ''.pfc'' files.</ref> pass [[Legal_considerations_for_fonts|legal checks]] and are packaged according to [[Packaging:FontsPolicy]]. | ||
== Discussion == | |||
* we already have specific rules for -static and -headers | |||
* fonts are easier to miss than headers, even experienced packagers have forgotten to look for them in the past | |||
* fonts are quite common as the current distro audit shows | |||
* fonts are non-trivial to package properly, we had to write specific macros because many packagers were messing up scriptlets | |||
* the font autoinstall F11 feature assumes fonts are packaged according to guidelines and will produce unexpected results if they're not | |||
* a broken font deployment can break all GUI apps | |||
* fonts have been pirated before mp3 was defined and fonts which origin has not been checked by the packager are a legal [[TomCallaway/TexLive2008|risk]] | |||
<noinclude> | <noinclude> | ||
Notes: | Notes: | ||
Line 11: | Line 24: | ||
{{:Fonts_SIG_signature}}[[Category:Fonts packaging guideline change proposals|2009-01-22, Review guidelines]]</noinclude> | {{:Fonts_SIG_signature}}[[Category:Fonts packaging guideline change proposals|2009-01-22, Review guidelines]]</noinclude> | ||
[[Category:Archived packaging guideline drafts]] |
Latest revision as of 18:53, 27 February 2009
Since fonts have specific packaging and legal requirements, but are often hidden deep into other stuff, make sure the packager checked for their existence (to avoid needing a new painful audit in a few releases).
The change
Add the following line to Packaging/ReviewGuidelines:
- MUST: Font files[1] pass legal checks and are packaged according to Packaging:FontsPolicy.
Discussion
- we already have specific rules for -static and -headers
- fonts are easier to miss than headers, even experienced packagers have forgotten to look for them in the past
- fonts are quite common as the current distro audit shows
- fonts are non-trivial to package properly, we had to write specific macros because many packagers were messing up scriptlets
- the font autoinstall F11 feature assumes fonts are packaged according to guidelines and will produce unexpected results if they're not
- a broken font deployment can break all GUI apps
- fonts have been pirated before mp3 was defined and fonts which origin has not been checked by the packager are a legal risk
Notes:
- ↑ .otf, .ttf, .ttc, .pfa, .pfb, .pfc files.