LaTeX2rtf is a translator program which is intended to translate a LaTeX document (precisely: the text and a limited subset of LaTeX tags) into the RTF format which can be imported by several textprocessors (including Microsoft Word for Windows and Word for Macintosh). I'm contributing an ebuild for Latex2rtf version 1.9.14 This application would be app-text/latex2rtf Also I'm submiting my version of the Makefile (needed for my ebuild) Please put it it on /usr/portage/latex2rtf-1.9.14/files/Makefile (I prefer this to patching the Makefile, since it will make it easier the upgrades, and there are many modifications) The documentation goes in /usr/share/doc/latex2rtf-1.9.14 (only the text version and the man page are installed by default; html, info and pdf versions are also installed if doc flag is USEd) The configuration files for different languages goes in /usr/share/latex2rtf/ Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 25609 [details] my ebuild for latex2rtf
Created attachment 25610 [details] my Makefile for latex2rtf put it in /usr/portage/latex2rtf-1.9.14/files/Makefile
Hi, thanks for submitting the ebuild. However, there are several things I should mention before taking it to Portage tree. 1) app-text/tetex should be virtual/tetex, otherwise app-text/ptex and app-text/cstetex users won't take benefit of the package ;) 2) Write ${P}.tar.gz instead of ${PN}-${PV}.tar.gz. ${P} is expaned to ${PN}-${PV} but it looks cleaner and matches our convention. Also, if it is hosted by sourceforge, we could write it as SRC_URI="mirror://sourceforge/latex2rtf/...". It will grab files from one of sourceforge mirrors, which is better than specifying only one mirror. 3) Although there are many ways to write `use' command in if - then clause, it would be better to use if use doc ; then ... fi or if [ `use doc` ]; then ... fi or if [ -n "`use doc`" ] then ... fi or something similar. It is because if (use doc); then invokes subshell to check whether use flag is set, but we don't actually need to run subshell for that purpose.
Created attachment 26274 [details] modified ebuild Ok, I'm sending to you a modified ebuild acording to your remarks. (excuse me, I don't know well the details of the Gentoo standards) Please note that I've renamed my Makefile to Makefile-1.9.14 in order to make easier future updates
Created attachment 26275 [details] a modified version of the Makefile I've renamed it to Makefile-1.9.14 to make it easier updates (by identifying the package version) Also I've deleted some non necesary lines with anoying messages
I committed your ebuild(1.9.14) and the latest one (1.9.15) to Portage. Despite your first comment about creating Makefile, I extracted a diff from you Makefile-1.9.14 and applied it. This is because it makes it easier to upgrade (Makefile for 1.9.14 doesn't work for 1.9.15, but the patch for 1.9.15 works for 1.9.14 and vice versa). Also, I modified your patch because man and info directories in Gentoo are not /usr/man and /usr/info but /usr/share/man and /usr/share/info. Thanks for contributing the ebuild and giving us informative comments.
