Red Hat Bugzilla – Bug 342581
multiarch conflicts in mecab
Last modified: 2014-03-16 23:10:25 EDT
mecab (or one of its subpacakges) has multiarch conflicts when installed for both i386 and x86_64 in the Fedora development tree. For help in resolving them, see http://fedoraproject.org/wiki/PackagingDrafts/MultilibTricks.
file /etc/mecabrc from install of mecab-0.96-1.fc8.2 conflicts with file from package mecab-0.96-1.fc8.2
file /usr/bin/mecab-config from install of mecab-devel-0.96-1.fc8.2 conflicts with file from package mecab-devel-0.96-1.fc8.2
(Note that this is an automated bug filing.)
It would be nice to have these bugs fixed by the beta of Fedora 9.
This should be fixed, whether by changing the files or changing the packaging.
Please don't expect that mecab(-devel) can be multi-arch installable.
Why not? Hundreds of other apps are.
Similar with hyperestraier, mecab reads text files and creates/reads
something like database files, which are *arch dependent*.
So, for example if
- a package using 32 bit mecab library creates some files
- and another package using 64 bit mecab library reads the files
it is hazardous. So generally mecab isn't multiarch installable.
However, we install devel as multiarch so things can build against the devel
libraries - how does that prevent this?
- I cannot figure out why you want to install two arch devel packages
even if mecab libraries are not multiarch installable.
Any strong rationale, approved by packaging committee?
Moreover, /usr/bin/mecab-config contains the information of
the data used by mecab library installed, not just pointing the
place of the libraries or else.
So I cannot find out any ratiorate for fixing multiarch conflict
even if mecab does not expect multiarch install.
Closing as WONTFIX again for now.
- Please discuss what we should fix for what purpose on some mailing