lhs2tex is a pretty printer for LaTeX-style Haskell literate scripts. First stab at an ebuild to be attached.
Created attachment 27545 [details] ebuild for lhs2tex
george who's our haskell guy again?
Nice that someone requests it, as I am the co-author of the tool ;) I am willing to add it to portage and maintain it, but because this is at the border between being Haskell-related and TeX-related, there are some questions that need to be answered, and I could use the help of the text-markup team here (adding you as cc). (1) placement of the package; could be app-text, dev-tex, or dev-haskell. Although dev-tex contains lgrind, which is a similar tool for C-like languages, I would argue much in favor of dev-haskell, because it is a small category and I doubt that many non-Haskell people will be interested in it. (2) lhs2TeX depends on a LaTeX package (polytable.sty), which is included in the lhs2TeX distribution, but also available separately from CTAN. polytable.sty itself depends on another LaTeX package (lazylist.sty), which is also included or available from CTAN. Neither of these are in portage. I think it would be cleaner to create separate packages for both of them, even though they are unlikely to be needed for anything except lhs2tex (but one never knows), to be placed in dev-tex/lazylist and dev-tex/polytable. I will attach my own versions of these three ebuilds -- to summarize: dev-haskell/lhs2tex-1.9 dev-tex/polytable-0.7.2 dev-tex/lazylist-1.0a The latter two are CTAN downloads. For testing, I have mirrored the files on in my own homedir, but if they are indeed added to Gentoo, they should be put on a Gentoo mirror. ks
Created attachment 27570 [details] ks's ebuild for lhs2tex
Created attachment 27571 [details] ebuild for polytable
Created attachment 27572 [details] ebuild for lazylist
I've just noted that there are a few minor bugs that slipped through the ebuilds I submitted: The homepage of the lhs2tex ebuild is wrong, it is correct in Sam's version. The homepage and description of the polytable ebuild are wrong. I will not reattach the updated versions because the changes are too minor. ks
I'm all for it. I think dev-haskell is ok for lhs2tex. Could you add all of them and assign text-markup herd as secondary maintaining herd? primary maintaining herd should be haskell wherever they will be placed ;) Alternatively, you may want to write your name as a maintainer and add text-markup as a maintaining herd. P.S. S="${WORKDIR}/lhs2tex-${PV}" isn't necessary because S is set to ${WORKDIR}/${P} (and ${P} expands to ${PN}-${PV}, where ${PN} is lhs2tex here) by default. Also, insinto /usr/share/doc/${PF} isn't needed since dodoc installs documentation there by default.
I just added all three ebuilds as agreed to CVS. usata, thanks for spotting the glitches in the ebuild. Testing welcome. Closing the bug. ks
