2016-03-05 10:55:30 +01:00
|
|
|
# $NetBSD: Makefile,v 1.23 2016/03/05 09:55:30 ryoon Exp $
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
|
2016-03-05 10:55:30 +01:00
|
|
|
DISTNAME= dblatex-0.3.7
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
CATEGORIES= textproc
|
|
|
|
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE:=dblatex/}
|
|
|
|
EXTRACT_SUFX= .tar.bz2
|
|
|
|
|
|
|
|
MAINTAINER= pkgsrc-users@NetBSD.org
|
|
|
|
HOMEPAGE= http://dblatex.sourceforge.net/
|
|
|
|
COMMENT= DocBook to LaTeX Publishing
|
2012-02-15 23:06:02 +01:00
|
|
|
LICENSE= gnu-gpl-v2
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
|
|
|
|
DEPENDS+= ImageMagick-[0-9]*:../../graphics/ImageMagick
|
2015-04-27 14:42:47 +02:00
|
|
|
DEPENDS+= tex-latex-bin-[0-9]*:../../print/tex-latex-bin
|
|
|
|
DEPENDS+= makeindexk-[0-9]*:../../textproc/makeindexk
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
DEPENDS+= libxslt-[0-9]*:../../textproc/libxslt
|
2015-05-06 12:25:40 +02:00
|
|
|
DEPENDS+= texlive-collection-latex-[0-9]*:../../meta-pkgs/texlive-collection-latex
|
2008-06-19 18:35:22 +02:00
|
|
|
DEPENDS+= tex-ifxetex-[0-9]*:../../print/tex-ifxetex
|
2015-04-27 14:42:47 +02:00
|
|
|
DEPENDS+= tex-anysize-[0-9]*:../../print/tex-anysize
|
|
|
|
DEPENDS+= tex-appendix-[0-9]*:../../print/tex-appendix
|
|
|
|
DEPENDS+= tex-changebar-[0-9]*:../../print/tex-changebar
|
|
|
|
DEPENDS+= tex-fancybox-[0-9]*:../../print/tex-fancybox
|
|
|
|
DEPENDS+= tex-fancyvrb-[0-9]*:../../print/tex-fancyvrb
|
|
|
|
DEPENDS+= tex-float-[0-9]*:../../print/tex-float
|
|
|
|
DEPENDS+= tex-footmisc-[0-9]*:../../print/tex-footmisc
|
|
|
|
DEPENDS+= tex-jknapltx-[0-9]*:../../print/tex-jknapltx
|
|
|
|
DEPENDS+= tex-listings-[0-9]*:../../print/tex-listings
|
|
|
|
DEPENDS+= tex-multirow-[0-9]*:../../print/tex-multirow
|
|
|
|
DEPENDS+= tex-overpic-[0-9]*:../../print/tex-overpic
|
|
|
|
DEPENDS+= tex-pdfpages-[0-9]*:../../print/tex-pdfpages
|
|
|
|
DEPENDS+= tex-rotating-[0-9]*:../../print/tex-rotating
|
|
|
|
DEPENDS+= tex-stmaryrd-[0-9]*:../../fonts/tex-stmaryrd
|
|
|
|
DEPENDS+= tex-subfigure-[0-9]*:../../print/tex-subfigure
|
|
|
|
DEPENDS+= tex-titlesec-[0-9]*:../../print/tex-titlesec
|
|
|
|
DEPENDS+= tex-wasysym-[0-9]*:../../fonts/tex-wasysym
|
2015-09-10 01:48:11 +02:00
|
|
|
DEPENDS+= tex-ec-[0-9]*:../../fonts/tex-ec
|
|
|
|
DEPENDS+= tex-rsfs-[0-9]*:../../fonts/tex-rsfs
|
|
|
|
DEPENDS+= tex-eepic-[0-9]*:../../graphics/tex-eepic
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
|
|
|
|
USE_LANGUAGES= # none
|
2014-12-10 13:27:27 +01:00
|
|
|
USE_TOOLS+= gmake
|
|
|
|
|
|
|
|
.include "options.mk"
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
|
2012-11-03 21:33:04 +01:00
|
|
|
REPLACE_PYTHON+= scripts/dblatex lib/dbtexmf/dblatex/xetex/*.py
|
2015-12-05 22:25:27 +01:00
|
|
|
PYTHON_VERSIONS_INCOMPATIBLE= 33 34 35 # not yet ported as of 0.3.2
|
2011-07-05 01:08:22 +02:00
|
|
|
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
SUBST_CLASSES+= man
|
|
|
|
SUBST_MESSAGE.man= Fixing man page installation path.
|
|
|
|
SUBST_STAGE.man= pre-configure
|
|
|
|
SUBST_FILES.man= setup.py
|
|
|
|
SUBST_SED.man+= -e 's,share/man/man1,${PKGMANDIR}/man1,'
|
|
|
|
SUBST_SED.man+= -e "s,'python','${PYTHONBIN}',"
|
|
|
|
|
2012-11-03 21:33:04 +01:00
|
|
|
do-test:
|
|
|
|
cd ${WRKSRC}/tests/mathml && gmake
|
2013-04-08 13:17:08 +02:00
|
|
|
|
2011-07-05 01:08:22 +02:00
|
|
|
.include "../../lang/python/application.mk"
|
2014-05-29 10:58:24 +02:00
|
|
|
.include "../../lang/python/egg.mk"
|
Initial import of dblatex-0.2.7:
Dblatex started as a DB2LaTeX clone, but since then many things
have changed and new features have been added or (hopefully)
improved. Now, the portion of shared code is small if any, and the
dblatex purpose is different from DB2LaTeX on these points:
* The project is end-user oriented, that is, it tries to hide as
much as possible the latex compiling stuff by providing a single
clean script to produce directly DVI, PostScript and PDF output.
* The actual output rendering is done not only by the XSL stylesheets
transformation, but also by a dedicated LaTeX package. The goal is
to allow a deep LaTeX customisation without changing the XSL
stylesheets.
* Post-processing is done by Python, to make publication faster,
convert the images if needed, and do the whole compilation.
2007-09-08 12:25:48 +02:00
|
|
|
.include "../../mk/bsd.pkg.mk"
|