On Sun, Aug 16, 2009 at 11:40:03PM +0200, Rene Engelhard wrote:
> Package: myspell-nl
> Severity: important
> Version: 1:1.10-2
> 
> http://lists.debian.org/debian-release/2009/08/msg00025.html received no
> objections so we gonna start it with STEP 1.
> Actually, it already started, I already uploaded some packages with this.
> 
> So please move your dicts tp /usr/share/hunspell and add compatibility        
>   
> symlinks from /usr/share/myspell/dicts (And *do* keep eventual compat         
>   
> symlinks for either Mozilla or OOo3 in the new location, too, and also        
>   
> keep compat symlinks for them).                                               
>   
Please be more precise in what symlinks you except to end up
with.  You seem to be talking about:
- symlinks in /usr/share/myspell/dicts to /usr/share/hunspell
- symlinks in /usr/share/hunspell to Mozilla and OOo3, but to
  where?
- And then we need to still keep some others that we already have?

> If you use installdeb-myspell there's two options                             
>   
>  - Either wait until we uploaded a new dictionaries-common with updated       
>   
>    installdeb-myspell                                                         
>   
Why do you file bugs before you upload that?

Can this be done using a binNMU in that case?

Note that we ship 2 files in /usr/share/myspell/dicts:
nl.add and nl.dic.  And then we have a bunch of symlinks
for them.  I don't see how a new installdeb-myspell will
fix that?

Do we still need the myspell-nl.info-myspell file?  It
seems we never fixed that one, it seems to be only needed
for openoffice < 3, and it probably was a better way to
list the support country codes in the first place.

What I would like to get fixed is the need for both
nl_BE and nl-BE.

>  - Do the necessary steps on your own.                                        
>   
I don't see an other option, but I first need to know
exactly what you expect.


Kurt




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to