inkscape @0.92.2: library dependency aspell prevents build of hunspell-en_US and hunspell-de_DE due to conflict with ispell

[maehne (Torsten Maehne)]

The build of hunspell-en_US and hunspell-de_DE requires the port ispell to be installed. Unfortunately, inkscape forces the installation of port aspell by specifying it as a library dependency. However, this direct dependency on aspell doesn't seem to be necessary because according to the ​inkscape wiki, the spell checking is done through gtkspell. This is already reflected in the inkscape port through the library dependency on gtkspell2. gtkspell2 itself does use enchant for unified access to different spell checkers (applespell, aspell, ispell, myspell). Is there another reason to force installation of aspell or can the dependency simply dropped?

[Schamschula (Marius Schamschula)]

This is an issue I ran into when first porting hunspell-de_DE. Unfortunately, even though aspell also supplies an ispell binary, it is missing capabilities required to build hunspell-de_DE. I just temporarily deactivated aspell and activated ispell. ispell is only needed during installation, so aspell can be reactivated afterward.

[raimue (Rainer Müller)]

Inkscape links with aspell, so the dependency is in fact correct:

$ otool -L /opt/local/bin/inkscape |grep aspell
	/opt/local/lib/libaspell.15.dylib (compatibility version 17.0.0, current version 17.5.0)

For reference, the reasons for this dependency were discussed previously in ticket:51287#comment:18, which also contains more details on spellchecking in inkscape.

[maehne (Torsten Maehne)]

Thanks a lot for your feedback to my bug report and pointing out why aspell is currently needed for the inkscape port! I hope that the issue will be cleaned up in the upstream implementation some day in the not too far future. Thanks also for the workaround of deactivating aspell for installing hunspell-de_DE. I did that, but found it inconvenient enough to report this issue.

[udbraumann]

I wonder why you think that hunspell-en_US is requiring ispell. In fact it requires aspell. However, I noticed some serious trouble on my 10.5.8 PPC system while upgrading hunspell-dict-en_US @2006-02-07_0 to hunspell-en_US @2017.08.24_1:

...
:info:build prep
:info:build creating en_US.dic
:info:build Can't locate object method "newdir" via package "File::Temp" at ../speller/munch-list line 47, <F> line 1.
:info:build Can't locate object method "newdir" via package "File::Temp" at ../speller/munch-list line 47, <F> line 1.
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_hunspell-en/hunspell-en_US/work/scowl-2017.08.24/speller" && ./make-hunspell-dict -all
:info:build Exit code: 255
:error:build Failed to build hunspell-en_US: command execution failed
:debug:build Error code: CHILDSTATUS 16647 255
...

To be honest, I have no idea the "newdir"method is missing. I attach the respective main.log.

[udbraumann]

Log file for hunspell-en_US

[Schamschula (Marius Schamschula)]

Replying to udbraumann:

I wonder why you think that hunspell-en_US is requiring ispell. In fact it requires aspell. However, I noticed some serious trouble on my 10.5.8 PPC system while upgrading hunspell-dict-en_US @2006-02-07_0 to hunspell-en_US @2017.08.24_1:

...
:info:build prep
:info:build creating en_US.dic
:info:build Can't locate object method "newdir" via package "File::Temp" at ../speller/munch-list line 47, <F> line 1.
:info:build Can't locate object method "newdir" via package "File::Temp" at ../speller/munch-list line 47, <F> line 1.
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_textproc_hunspell-en/hunspell-en_US/work/scowl-2017.08.24/speller" && ./make-hunspell-dict -all
:info:build Exit code: 255
:error:build Failed to build hunspell-en_US: command execution failed
:debug:build Error code: CHILDSTATUS 16647 255
...

To be honest, I have no idea the "newdir"method is missing. I attach the respective main.log.

This should be a separate ticket, as it does not pertain to inkscape.

The issue in this ticket is that the hunspell-en_US dictionary requires aspell to be built, but inkscape requires ispell at runtime. aspell conflicts with ispell.

[udbraumann]

Replying to Schamschula:

This should be a separate ticket, as it does not pertain to inkscape.

The issue in this ticket is that the hunspell-en_US dictionary requires aspell to be built, but inkscape requires ispell at runtime. aspell conflicts with ispell.

Well, this also means that the ticket title is wrong, or at least is misleading, as inscape's library dependency aspell does not prevent building of hunspell-en_US, but only of hunspell-de_DE (and other hunspell-de_*)

I would open a new ticket if I would know some maintainer of hunspell-en_US (or hunspell-en_*).

[Christopher Nielsen <mascguy@…>]

In 0af172de7ab880c9fc83905dfc50df1d0af2d0f7/macports-ports (master):

inkscape-devel: update to 1.1.2

• Credit to: @evanmiller

See: #50210
See: #51287
See: #51407
See: #54944
See: #60927
See: #61404
See: #64660

[evanmiller (Evan Miller)]

In d5bc993e56a90910b79609231a5b39a92ab59095/macports-ports (master):

inkscape: update to 1.1.2

Closes: #50210
Closes: #51287
Closes: #51407
Closes: #54944
Closes: #60927
Closes: #61404
Closes: #64660