Update Portfile - pandoc 0.44

[jgm@…]

Modified pandoc's Portfile in the following ways:

+ bumped version to 0.43 (pandoc 0.43 is five times faster than 0.42) + updated md5 sum + changed build-target to 'build-all' and destroot.target to 'install-all':

this installs haskell libraries and library documentation, in addition to the executable and user documentation.

+ added haddock as a build dependency (it is needed to build the library

documentation)

[jgm@…]

Since I've now released 0.44 (which fixes a critical bug in the debian build process), I attach here a new diff from the Portfile that is currently in the repository (for pandoc 0.42). The diff above for 0.43 may be ignored.

[jgm@…]

I've fixed a minor mistake in the Portfile.diff (the URL for pandoc's home page was incorrect).

[boeyms@…]

Everything seems fine except that the pandoc executable itself doesn't get installed (while hsmarkdown, html2markdown and markdown2pdf do). Would you be able to fix this?

[jgm@…]

Turns out there was a problem with the way the Makefile handles DESTDIR. The pandoc executable and library files were getting copied directly to the /opt/local tree, not to the destroot. Also, the library was not getting registered properly; this must be done in the activate phase, using a register.sh script generated in the destroot phase.

I have provided a new Portfile.diff that fixes all these problems.

[jgm@…]

Postscript: I have used the Portfile for devel/missingh as a model for the destroot and post-activate phases.

[boeyms@…]

Unfortunately this Portfile will now not work with the trunk version of MacPorts, as the ability for Portfiles to call Tcl's cd proc has been removed (it apparently changes the working directory of the entire Tcl interpreter). Unfortunately, I don't know what the normal working directory is when port is invoked. If it's not possible to rewrite the Portfile's custom destroot stage to work independently of the normal working directory, you could package into the tarball a script that does it (by default the Tcl interpreter forks a process that cd's to ${worksrcpath}). You could also use the system proc made available to Portfiles (see portfile(7)), though I don't recall whether this was being frowned upon as well.

[jgm@…]

New Portfile.diff, not using cd

[jgm@…]

I've uploaded a new version (Portfile.2.diff) that does not use Tcl's cd.

[boeyms@…]

Committed in r29630. Thanks again, and sorry for the bother.

[(none)]

Milestone Port Updates deleted