From Fedora Project Wiki
(Add detailed description)
 
(12 intermediate revisions by the same user not shown)
Line 26: Line 26:
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.  
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release.  
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". -->
Note that motivation for the change should be in the Motivation section below, and this part should answer the question "What?" rather than "Why?". -->
There are `font(:lang=...)` auto-generated dependency for fonts packages and packages that requires particular languages to get things working has those dependencies to pull it in. but that pulls packages in randomly and doesn't necessarily provide better result. particuarly when they don't have any fonts installed for those languages.
There are `font(:lang=...)` auto-generated dependency for fonts packages. it is used as a dependency identifier to satisfy a certain language requirement. but this way didn't guarantee qualities because what fonts packages is going to be pulled in is unreliable.


So this proposes to replace it with langpacks instead, which has proper dependencies for fonts and improve the user experience around fonts with applications.
So this proposes to replace it with langpacks instead, which has proper dependencies for fonts and improve the user experience around fonts with applications.
Line 48: Line 48:


== Current status ==
== Current status ==
* Targeted release: [[Releases/31 | Fedora 31 ]]  
* Targeted release: [[Releases/32 | Fedora 32 ]]  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
* Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page  
Line 61: Line 61:


== Detailed Description ==
== Detailed Description ==
The language based meta information about font dependency was introduced since Fedora 11. that was helpful to find out a font for missing glyphs through PackageKit and was useful for minority languages. but the given result by it wasn't much better under the certain condition.
The language based meta information about font dependency was introduced since Fedora 11. that was helpful to find out a font for missing glyphs through PackageKit and was useful for minority languages because we didn't have fonts packages for them so much. but the user experience wasn't that better under the certain condition.


Users can't predict what fonts will be installed. this may gives us worst result particularly when no fonts for the requested language is installed and/or is majority languages that has too many fonts such as English, because this logic doesn't ensure the quality of fonts nor preferred fonts we expect to get installed by default.
Users can't predict what fonts will be installed. this may gives us worst result particularly when no fonts for the requested language is installed and/or is majority languages that has too many fonts such as English, because this logic doesn't guarantee the quality of fonts nor preferred fonts we expect to get installed by default.
This random dependency sometimes introduces unexpected result too. it might be able to pulls packages in to dependencies from external repositories. this may particularly be a problem when composing ISOs.
This random dependency sometimes introduces unexpected result too so that it's likely to happen that dependencies may be satisfied from external repositories. this may particularly be a problem when composing ISOs.


So this Changes proposal aims to improve the user experience around font dependencies by replacing it by Langpacks instead. Langpacks contains various dependencies to use for certain languages, including dependencies for default fonts. so it will resolves the above issues.
So this Changes proposal aims to improve the user experience around font dependencies by replacing it to Langpacks instead. Langpacks contains various dependencies to use for certain languages, including dependencies for default fonts. so it will resolves the above issues.


Specifically speaking, currently font dependency is generated like this:
<pre>
$ fc-query -f %{=pkgkit}  /usr/share/fonts/dejavu/DejaVuSans.ttf
font(dejavusans)
font(:lang=aa)
font(:lang=ab)
...
</pre>
and at the build time, it is transformed to:<pre>
Provides: font(dejavusans)
Provides: font(:lang=aa)
Provides: font(:lang=ab)
...</pre>
After this proposal, the above result will be:
<pre>
Provides: font(dejavusans)
</pre>
and then add `Provides: font(:lang=...)` line to corresponding sub-packages langpacks-core-*.
So asking for a font for a certain language through PackageKit will be achieved by langpacks-core-* instead of a random font package.
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->


== Benefit to Fedora ==
== Benefit to Fedora ==
 
This proposal provides reliable, predictable, and consistencies in dependencies about fonts.
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
    
    
Line 102: Line 125:
== Scope ==
== Scope ==
* Proposal owners:
* Proposal owners:
** Update fontconfig to drop `font(:lang=...)` from the alias of the formatter for `%{=pkgkit}`
** Add a line of `Provides: font(:lang=...)` to each `langpacks-core-...`. for instance, `Provides: font(:lang=hi)` need to be added to `langpacks-core-hi`.
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Other developers: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
<!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] all of fonts packages must be rebuilt so that the above change in fontconfig can be reflected to all of fonts packages. <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES -->
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.  
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings -->


* Policies and guidelines: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Policies and guidelines: N/A <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->
<!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. -->


* Trademark approval: N/A (not needed for this Change)
* Trademark approval: N/A
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://fedorahosted.org/council/ ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->


== Upgrade/compatibility impact ==
== Upgrade/compatibility impact ==
Some packages may be installed after upgrading if corresponding langpacks-core-* packages isn't yet installed.
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== How To Test ==
== How To Test ==
Line 140: Line 166:
-->
-->


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
# Check dependencies in langpacks-core-*. they must have corresponding `Provides: font(:lang=...)` line when asking with `rpm -q --provides`.
N/A (not a System Wide Change)  
# Check dependencies in fonts packages. they must contain no `Provides: font(:lang=...)` lines


== User Experience ==
== User Experience ==
Users may see better fonts for certain language when they need to install a set of fonts for certain language support through PackageKit or package dependencies from others.
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
<!-- If this change proposal is noticeable by users, how will their experiences change as a result?


Line 156: Line 184:


== Dependencies ==
== Dependencies ==
* fontconfig
* langpacks
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)


== Contingency Plan ==
== Contingency Plan ==


<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency mechanism: (What to do?  Who will do it?) Proposal owners will revert all of changes and rebuild all of fonts packages to add back deps <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
<!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
* Contingency deadline: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Contingency deadline: the beta freeze <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks release? No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Blocks product? product <!-- Applicable for Changes that blocks specific product release/Fedora.next -->
* Blocks product? N/A <!-- Applicable for Changes that blocks specific product release/Fedora.next -->


== Documentation ==
== Documentation ==
Line 175: Line 202:


<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
N/A (not a System Wide Change)
N/A


== Release Notes ==
== Release Notes ==
Line 191: Line 218:


<!-- Select proper category, default is Self Contained Change -->
<!-- Select proper category, default is Self Contained Change -->
[[Category:SelfContainedChange]]
[[Category:SystemWideChange]]
<!-- [[Category:SystemWideChange]] -->

Latest revision as of 05:28, 27 December 2019


Font Dependencies to Langpacks

Summary

There are font(:lang=...) auto-generated dependency for fonts packages. it is used as a dependency identifier to satisfy a certain language requirement. but this way didn't guarantee qualities because what fonts packages is going to be pulled in is unreliable.

So this proposes to replace it with langpacks instead, which has proper dependencies for fonts and improve the user experience around fonts with applications.

Owner

  • Name: Akira TAGOH
  • Email: tagoh@redhat.com
  • Release notes owner:

Current status

  • Targeted release: Fedora 32
  • Last updated: 2019-12-27
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The language based meta information about font dependency was introduced since Fedora 11. that was helpful to find out a font for missing glyphs through PackageKit and was useful for minority languages because we didn't have fonts packages for them so much. but the user experience wasn't that better under the certain condition.

Users can't predict what fonts will be installed. this may gives us worst result particularly when no fonts for the requested language is installed and/or is majority languages that has too many fonts such as English, because this logic doesn't guarantee the quality of fonts nor preferred fonts we expect to get installed by default. This random dependency sometimes introduces unexpected result too so that it's likely to happen that dependencies may be satisfied from external repositories. this may particularly be a problem when composing ISOs.

So this Changes proposal aims to improve the user experience around font dependencies by replacing it to Langpacks instead. Langpacks contains various dependencies to use for certain languages, including dependencies for default fonts. so it will resolves the above issues.

Specifically speaking, currently font dependency is generated like this:

$ fc-query -f %{=pkgkit}  /usr/share/fonts/dejavu/DejaVuSans.ttf
font(dejavusans)
font(:lang=aa)
font(:lang=ab)
...

and at the build time, it is transformed to:

Provides: font(dejavusans)
Provides: font(:lang=aa)
Provides: font(:lang=ab)
...

After this proposal, the above result will be:

Provides: font(dejavusans)

and then add Provides: font(:lang=...) line to corresponding sub-packages langpacks-core-*.

So asking for a font for a certain language through PackageKit will be achieved by langpacks-core-* instead of a random font package.

Benefit to Fedora

This proposal provides reliable, predictable, and consistencies in dependencies about fonts.

Scope

  • Proposal owners:
    • Update fontconfig to drop font(:lang=...) from the alias of the formatter for %{=pkgkit}
    • Add a line of Provides: font(:lang=...) to each langpacks-core-.... for instance, Provides: font(:lang=hi) need to be added to langpacks-core-hi.


  • Other developers: N/A
  • Policies and guidelines: N/A
  • Trademark approval: N/A

Upgrade/compatibility impact

Some packages may be installed after upgrading if corresponding langpacks-core-* packages isn't yet installed.


How To Test

  1. Check dependencies in langpacks-core-*. they must have corresponding Provides: font(:lang=...) line when asking with rpm -q --provides.
  2. Check dependencies in fonts packages. they must contain no Provides: font(:lang=...) lines

User Experience

Users may see better fonts for certain language when they need to install a set of fonts for certain language support through PackageKit or package dependencies from others.


Dependencies

  • fontconfig
  • langpacks

Contingency Plan

  • Contingency mechanism: (What to do? Who will do it?) Proposal owners will revert all of changes and rebuild all of fonts packages to add back deps
  • Contingency deadline: the beta freeze
  • Blocks release? No
  • Blocks product? N/A

Documentation

N/A

Release Notes