From Fedora Project Wiki
(→‎Scope: update package list)
 
(13 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->


= Hunspell Dictionary dir change from myspell to hunspell =
= Hunspell Dictionary dir change =
<!-- The name of your change proposal -->
<!-- The name of your change proposal -->


== Summary ==
== Summary ==
<!-- 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 Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
<!-- 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 Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
Update Hunspell Dictionary dir from /usr/share/myspell/ to /usr/share/hunspell/
Update Hunspell Dictionary system directory from /usr/share/myspell/ to /usr/share/hunspell/


== Owner ==
== Owner ==
Line 16: Line 16:
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
* Email: <vishalvvr@fedoraproject.org>
* Email: <vishalvvr@fedoraproject.org>
* Name: [[User:Pnemade| Parag Nemade]]
* Email: <pnemade@redhat.com>
* Name: [[User:Petersen| Jens Petersen]]
* Email: <petersen@redhat.com>
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
-->
-->


== Current status ==
== Current status ==
[[Category:ChangePageIncomplete]]
[[Category:ChangeAcceptedF36]]
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- When your change proposal page is completed and ready for review and announcement -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
Line 39: Line 42:
ON_QA -> change is fully code complete
ON_QA -> change is fully code complete
-->
-->
* FESCo issue: <will be assigned by the Wrangler>
* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/H6DJQKXRQ47ABOPXMRMMEFEREATUZWS3/ devel thread]
* Tracker bug: <will be assigned by the Wrangler>
* FESCo issue: [https://pagure.io/fesco/issue/2730 #2730]
* Release notes tracker: <will be assigned by the Wrangler>
* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2041930 #2041930]
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/789 #789]


== Detailed Description ==
== Detailed Description ==
Line 83: Line 87:
* Proposal owners:
* Proposal owners:
<!-- 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?-->
In total there are `135` packages which is to be updated. libreoffice & Firefox are the two main applications and rest are mostly language dictionary packages.  
** PR for Hunspell package
*** Update dir name from myspell/ to hunspell/
*** <strike>Create symlink myspell (to have better backward compatibility)</strike>
** PRs for language dictionaries ([https://paste.opensuse.org/61121010 121 packages]):
*** Update “install dir” from myspell/ to hunspell/
** PRs for enchant, enchant2, icecat, kde packages, libreoffice, firefox, seamonkey, thunderbird:
*** Update dictionary usage path from myspell/ to hunspell/
** Test [https://copr.fedorainfracloud.org/coprs/vishalvvr/hunspell_symlink copr repo]


* Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Other developers: <!-- 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?-->
** merge PRs to update path in hunspell-* dictionaries
** Merge PRs to update path dictionary path for libreoffice & Firefox


* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
Line 121: Line 134:
3. What are the expected results of those actions?
3. What are the expected results of those actions?
-->
-->
1. Check if default installed dictionary path is `/usr/share/hunspell/` instead of `/usr/share/myspell/`
1. Check if default installed dictionary path is `/usr/share/hunspell/`


`$ hunspell -D` or `$ ls /usr/share/hunspell/`     
`$ hunspell -D` or `$ ls /usr/share/hunspell/`     
Line 129: Line 142:
`$ dnf install hunspell-hi`
`$ dnf install hunspell-hi`


`$ hunspell -D`  
`$ hunspell -D`


3. Test spellchecking working in desktop apps for your language (eg Libreoffice, Firefox, Gedit, Evolution, Thunderbird, KDE, Emacs, etc)
4. Spellchecking on commandline: aspell, hunspell, nuspell
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->


== User Experience ==
== User Experience ==

Latest revision as of 07:21, 28 March 2022


Hunspell Dictionary dir change

Summary

Update Hunspell Dictionary system directory from /usr/share/myspell/ to /usr/share/hunspell/

Owner

Current status

Detailed Description

In most of Linux distributions the standard Hunspell dictionary path is /usr/share/hunspell/ but in Fedora still has /usr/share/myspell/. This effort is to follow default standard to install all Hunspell dictionary into /usr/share/hunspell/ instead of /usr/share/myspell/.

Feedback

Benefit to Fedora

This will future proof Fedora to use the correct current location for hunspell spelling dictionaries.

Scope

  • Proposal owners:
    • PR for Hunspell package
      • Update dir name from myspell/ to hunspell/
      • Create symlink myspell (to have better backward compatibility)
    • PRs for language dictionaries (121 packages):
      • Update “install dir” from myspell/ to hunspell/
    • PRs for enchant, enchant2, icecat, kde packages, libreoffice, firefox, seamonkey, thunderbird:
      • Update dictionary usage path from myspell/ to hunspell/
    • Test copr repo
  • Other developers:
    • merge PRs to update path in hunspell-* dictionaries
    • Merge PRs to update path dictionary path for libreoffice & Firefox
  • Policies and guidelines: N/A (not needed for this Change)
  • Trademark approval: N/A (not needed for this Change)
  • Alignment with Objectives:

Upgrade/compatibility impact

How To Test

1. Check if default installed dictionary path is /usr/share/hunspell/

$ hunspell -D or $ ls /usr/share/hunspell/

2. Install any language dictionary and check if it getting installed into '/usr/share/hunspell/'

$ dnf install hunspell-hi

$ hunspell -D

3. Test spellchecking working in desktop apps for your language (eg Libreoffice, Firefox, Gedit, Evolution, Thunderbird, KDE, Emacs, etc)

4. Spellchecking on commandline: aspell, hunspell, nuspell

User Experience

User should not notice any difference: their applications should continue to work as expected after this directory migration.

Dependencies

Contingency Plan

  • Contingency mechanism: revert release back to /usr/share/myspell
  • Contingency deadline: Beta
  • Blocks release? No

Documentation

Release Notes