Abiword ebuild does not install the help files. These should be installed to /usr/share/AbiSuite-2.0/AbiWord/help/ but in fact the entile "help" directory is not there. As a result, no help is available from any part of the application. Reproducible: Always Steps to Reproduce: 1. Start AbiWord 2. Press F1 for Help or use the menu 3. Actual Results: Mozilla comes up with an error about file:///usr/share/AbiSuite-2.0/AbiWord/help/en-US/... not found. Expected Results: Mozilla should start with the top-level help files. I have read through the ebuild and see nothing in particular relating to help files, so it seems the ebuild expects they will be installed as part of the normal build.
care to find out how to get them back in for us, we're pressed on time here.
Okay, finally figured it out after about an hour of playing with sed :) Please stick this at the bottom of src_install(): # Build documentation cd ${WORKDIR}/${P}/abiword-docs sed -e 's!prefix = /usr/local!prefix = /usr!g' Makefile > Makefile.new mv Makefile.new Makefile emake || die As always, thanks to foser for his guidance :) P.S. if you need a diff I can provide one but I don't think it is necessary. Also, are there any plans on putting abiword-2.1 in the ~arch tree?
hmm ok sorry for the delay. I tried this fix with 2.0.3, but it ends in the sandbox.
No sandbox errors here, can anyone else confirm?
Ugh, my mistake, I was merging with -sandbox. This is rather easy to fix... # Build documentation cd ${WORKDIR}/${P}/abiword-docs sed -e 's!prefix = /usr/local!prefix = /usr!g' Makefile > Makefile.new mv Makefile.new Makefile make DESTDIR=${D}
just add abiword-2.0.3-r1 with the fix. Added a USE doc block around the doc installation part. Please test. Thanks khai for the fix.
My only question here is, why make this depend on the "doc" flag? That's described as "Adds extra documentation (API, Javadoc, etc.)", which could lead people (including me!) to think it does *not* mean you need to turn it on to get normal user help, such as what's supposed to pop up in AbiWord when you press <F1>. Shouldn't the user help be installed as a matter of course?
a reasonable point, but the docs installation is optional here, and optional to me means using a USE flag. The problem really lies in the vague description of the doc USE flag and maybe the lack of more specific USE flags for certain situations. But to me this is a problem that should be tackled in a wider context and only then implemented.
actually I sorta regret naming the "doc" flag just that, it should be named "apidoc". Normal user documentation should always be installed.
