[86791] trunk/dports/textproc/multimarkdown/Portfile

[Ryan Schmidt]

On Nov 4, 2011, at 08:00, singingwolfboy at macports.org wrote:

> Revision: 86791
>          http://trac.macports.org/changeset/86791
> Author:   singingwolfboy at macports.org
> Date:     2011-11-04 06:00:36 -0700 (Fri, 04 Nov 2011)
> Log Message:
> -----------
> multimarkdown: update to v3.2
> 
> Modified Paths:
> --------------
>    trunk/dports/textproc/multimarkdown/Portfile
> 
> Modified: trunk/dports/textproc/multimarkdown/Portfile
> ===================================================================
> --- trunk/dports/textproc/multimarkdown/Portfile	2011-11-04 10:52:19 UTC (rev 86790)
> +++ trunk/dports/textproc/multimarkdown/Portfile	2011-11-04 13:00:36 UTC (rev 86791)
> @@ -5,8 +5,8 @@
> name                multimarkdown
> set git_name        peg-${name}
> set git_author      fletcher
> -version             3.0b11
> -revision            3
> +version             3.2
> +revision            1

Don't change it now, but remember for future reference that the first revision of any version of a port should be 0 not 1, and this can be done by just removing the revision line.


> -#master_sites        https://github.com/${git_author}/${git_name}/tarball/${version}
> -#distname            ${git_author}-${git_name}-${version}-0-g92e0466
> -#worksrcdir          ${git_author}-${git_name}-8486af4
> -#checksums           md5     7814325404daa9b570b4506f8302c034 \
> -#                    sha1    42f6882bb55092c2b89aae124ac54a70dd0215d7 \
> -#                    rmd160  5c2b3f58b99196dd78128de25aef94fc2f7001e5
> 
> fetch.type          git
> git.url             https://github.com/${git_author}/${git_name}

What's the story about why this port fetches from git? Tarballs seem to be available, and I had tried to use the 3.2 tarball in my attempted update of this port. The problem I got was:


cd documentation; \
	../Support/Utilities/mmd_merge.pl index.txt > manual.txt; \
	../multimarkdown manual.txt > ../manual/index.html; \
	../multimarkdown -b -t latex manual.txt; \
	latexmk manual.tex; \
	latexmk -c manual.tex; \
	mv manual.pdf ../manual/mmd-manual.pdf; \
	cd ../manual; git add mmd-manual.pdf index.html; \
	git commit -m "update manual"; git push origin gh-pages; \
	rm ../documentation/manual.t*;
/bin/sh: ../Support/Utilities/mmd_merge.pl: No such file or directory
/bin/sh: ../manual/index.html: No such file or directory
/bin/sh: latexmk: command not found
/bin/sh: latexmk: command not found
mv: rename manual.pdf to ../manual/mmd-manual.pdf: No such file or directory
/bin/sh: line 0: cd: ../manual: No such file or directory
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git


Is this the reason? Does building the documentation require parts that are not in the tarball, that are only available via git?