dblatex fails with titlesec.sty not found error

[nortcele]

Since, r132311 dblatex fails to output a pdf file with a titlesec.sty not found error.

To reproduce:

# First clean macports to only get essential dependencies
sudo port uninstall installed
# Then install dblatex
sudo port install dblatex

Create a simple test.xml file with ie.:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
                    "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
]>


<article class="techreport" status="final">


<para>Just some blabla.</para>

</article>

Then use dblatex to create a pdf file from this file:

dblatex test.xml

The pdf creation fails.

[nortcele]

The problem could be circumvented by editing dblatex Portfile with:

--- Portfile.orig	2015-03-09 12:00:43.000000000 +0100
+++ Portfile	2015-03-09 14:40:23.000000000 +0100
@@ -3,6 +3,7 @@
 
 PortSystem          1.0
 PortGroup           python 1.0
+PortGroup           texlive 1.0
 
 name                dblatex
 version             0.3.5
@@ -69,7 +70,11 @@
 }
 
 post-activate {
-    system "${prefix}/bin/mktexlsr"
+    texlive.mktexlsr
+}
+
+post-deactivate {
+    texlive.mktexlsr
 }
 
 livecheck.type      regex

and reinstall dblatex.

[nortcele]

As titlesec.sty is part of textive-latex-extra, the latex update should have come from textive-latex-extra port.

[neverpanic (Clemens Lang)]

Doesn't texlive-latex-extra run mktexlsr? I agree we should use the texlive portgroup, though.

[neverpanic (Clemens Lang)]

Replying to cal@…:

Doesn't texlive-latex-extra run mktexlsr? I agree we should use the texlive portgroup, though.

I checked and it texlive-latex-extra already runs mktexlsr (by including the PortGroup, not changing defaults and running texlive.texmfport).

However, I recently removed a couple of .sty files dblatex used to install because they were shadowing newer versions provided by our texlive ports, and that might have left the cache in an incoherent state. I've applied your patch in r133761. Additionally, I increased the revision to fix this problem for all users that may still be experiencing it.