1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia-Private%5D%20Consolidation%20of%20the%20spelling%0A%09tools%20in%20Mageia&In-Reply-To=%3C4F09E80B.1080005%40mageia.org%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="011117.html">
<LINK REL="Next" HREF="011162.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia</H1>
<B>Anssi Hannula</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5BMageia-Private%5D%20Consolidation%20of%20the%20spelling%0A%09tools%20in%20Mageia&In-Reply-To=%3C4F09E80B.1080005%40mageia.org%3E"
TITLE="[Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia">anssi at mageia.org
</A><BR>
<I>Sun Jan 8 20:01:31 CET 2012</I>
<P><UL>
<LI>Previous message: <A HREF="011117.html">[Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia
</A></li>
<LI>Next message: <A HREF="011162.html">[Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11127">[ date ]</a>
<a href="thread.html#11127">[ thread ]</a>
<a href="subject.html#11127">[ subject ]</a>
<a href="author.html#11127">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 08.01.2012 16:19, Luc Menut wrote:
><i> Hello,
</I>><i>
</I>><i> first, sorry to reply so late, and when you have started to update
</I>><i> hunspell dictionaries packages.
</I>><i>
</I>><i> Le 21/12/2011 08:15, Kamil Rytarowski a écrit :
</I>>><i> Hello!
</I>><i> [...]
</I>>><i>
</I>>><i> There was a discuss on
</I>>><i> 1) preparing policies on hunspell-dictionaries
</I>>><i> 2) deprecate and kill myspell in Mga2
</I>>><i> 3) changing the default path of dictionaries, from /usr/share/myspell to
</I>>><i> /usr/share/hunspell (and to keep backward compatibility links in myspell
</I>>><i> directory)
</I>>><i> 4) to provide "enchant-dictionary" and "hunspell-dictionary" by every
</I>>><i> hunspell-dictionary
</I>>><i>
</I>>><i> So finally, I've prepared a first version of the policy
</I>>><i> <A HREF="https://wiki.mageia.org/en/Hunspell-dictionary_policy">https://wiki.mageia.org/en/Hunspell-dictionary_policy</A>
</I>>><i> If you like, please tell me your comments of it. Is it right? (Also: is
</I>>><i> the .spec correct?) When everything will be accepted then every
</I>>><i> hunspell-dictionary will be updated according to the policy.
</I>><i>
</I>><i> some comments about the policy:
</I>><i>
</I>><i> Version: 1.0
</I>><i> Release: %mkrel %{upstream_release}.%{rel}
</I>><i>
</I>><i> I don't think it will be possible to use Version 1.0 and upstream
</I>><i> version only in the release; most hunspell dictionaries already use
</I>><i> upstream version as version and have a version > 1.0.
</I>
Strong +1 from me for not using hardcoded Version 1.0, please instead
use the %upstream_release in Version.
I don't see any reason to break the versioning policy here.
><i> --
</I>><i>
</I>><i> #Mageia values: 1 - aspell, 2 - hunspell, 3 - language specific
</I>><i> Provides: enchant-dictionary = 2
</I>><i> Provides: hunspell-dictionary
</I>><i> Provides: dictionary-%{languagecode}
</I>><i>
</I>><i> about the version value of the provides: is the meaning (1 - aspell, 2 -
</I>><i> hunspell, 3 - language specific) really needed? is it currently used?
</I>
The intention was that when a package depended on enchant-dictionary,
urpmi would prefer language specific enchant dictionaries over hunspell
dictionaries over aspell dictionaries when presenting a list for the user.
><i> Because I think that it could be usefull that the versionned provides
</I>><i> indicates the location of the dictionary:
</I>><i> - current enchant-dictionary = 2 ->> /usr/share/dict/mozilla
</I>><i> - enchant-dictionary from hunspell ->> enchant-dictionary = 4 ->>
</I>><i> /usr/share/hunspell and /usr/share/myspell,
</I>><i> - enchant-dictionary from future hunspell without compatibility link in
</I>><i> /usr/share/myspell ->> enchant-dictionary = 5 ->> /usr/share/hunspell only,
</I>><i> - ...
</I>><i>
</I>><i> (it seems weird for me to use the same "enchant-dictionary = 2"
</I>><i> versionned provide, both for "deprecated" myspell dictionaries, and new
</I>><i> hunspell dictionaries.)
</I>><i>
</I>><i> if the versionned provides indicates the location, we can use it if
</I>><i> necessary in Conflicts or Requires in others packages.
</I>><i> e.g. currently Firefox searches dictionnaries in /usr/share/dict/mozilla
</I>><i> (myspell dictionaries). when we change this location, we could add a
</I>><i> Requires enchant-dictionary = 4.
</I>
IMO a better way to handle this would be
Provides: mozilla-dictionary
Provides: hunspell-dictionary
Provides: myspell-dictionary
based on which directories are contained in the package, since other
packages are generally interested in whether the package provides
dictionaries in a specific location. (i.e. a package using dictionaries
in /usr/share/hunspell doesn't care if there are some extra dictionaries
provided in other directories).
><i> same for hunspell-dictionary and dictionary-%{languagecode}, a
</I>><i> versionned provides could indicate the location of the dictionary.
</I>><i> if we want to be able to remove easily all the compatibility link in the
</I>><i> future, we should really consider this.
</I>><i>
</I>><i>
</I>>><i>
</I>>><i> PS. The changes of enchant will be proposed or accepted later, Funda has
</I>>><i> already prepared the package.
</I>><i>
</I>><i> new hunspell dictionaries provides enchant-dictionary and obsoletes
</I>><i> myspell dictionaries, but enchant still can't use the new hunspell
</I>><i> dictionaries. I think that it should be fixed ASAP, or we will release
</I>><i> an alpha 3 with broken spelling for lot of languages.
</I>><i> I propose the attached patches for enchant, so that enchant can use
</I>><i> dictionaries from /usr/share/hunspell, /usr/share/myspell, and
</I>><i> /usr/share/dict/ooo.
</I>><i> Anssi, Kamil, WDYT ?
</I>
Seems OK.
><i> same problem with firefox and thunderbird, they use dictionaries from
</I>><i> /usr/share/dict/mozilla = myspell dictionaries, that are obsoleted.
</I>><i> (Will we wait for the complete migration, to release alpha 3 ? )
</I>><i>
</I>><i> CC: Anssi, enchant and thunderbird maintainer
</I>><i> dmorgan, firefox maintainer
</I>><i>
</I>><i>
</I>><i> regards,
</I>><i> Luc
</I>><i>
</I>
--
Anssi Hannula
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="011117.html">[Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia
</A></li>
<LI>Next message: <A HREF="011162.html">[Mageia-dev] [Mageia-Private] Consolidation of the spelling tools in Mageia
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#11127">[ date ]</a>
<a href="thread.html#11127">[ thread ]</a>
<a href="subject.html#11127">[ subject ]</a>
<a href="author.html#11127">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
