On Sun, Jan 31, 2010 at 02:10:04PM +0100, Agustin Martin wrote:
> I am at a lenny box and cannot properly check now. If dependencies did
> not change too much from lenny to squeeze, I think the final
> recommends that is triggering the pull is that libhunspell-1.2-0
> recommends (myspell-en | myspell dictionary)  and that  libaspell15
> recomends (aspell-en|aspell dictionary).  What makes it loaded in
> lenny is a dependency chain like
> 
> libnotify1 -> notification-daemon -> libsexy2 -> libenchant1c2a ->
> (libaspell15,libhunspell-1.2-0)
> 
> I did not go above libnotify1 and did not look for recommends, so may
> be other branches.  Will try next week in a real sid box.

While still did not fully look at this in a sid box, similar chain seems
to happen. On the one hand libenchant requires aspell and hunspell libs
perverting enchant purpose

[#232335: Multiple engine requirement perverts purpose of enchant]

on other hand aspell and hunspell libs recommends dictionaries (thus pulling
dictionaries-common). And combined with all that, some of the packages
are linked to libenchant just to provide an additional functionality, but
would have worked well without it (however, that linking pulls libenchant as
dependency).

All that said, I do not see an easy way of addressing this problem by
breaking/fixing above dependency chain.

However, there is a possible alternative way of handling this. I had in mind
for some time some way or re-running language-based default value selection
when ispell dictionaries or wordlists are installed for the first time, even
if dictionaries-common is already installed, so they get a reasonable value.
I have doing some of the preliminary stuff and hope to make this work. If
so, this seems the best way to go. Will let you know about this.

Cheers,

-- 
Agustin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to