Date: Sun, 30 Dec 2012 10:35:54 +0000 From: Chris Rees <utisoft@gmail.com> To: Thomas Mueller <mueller23@insightbb.com> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: Stumbling block on updating devel/doxygen Message-ID: <CADLo839%2BMvBSt%2BN1zXKX44jOCPQ061bguNQ2NhX6TeK7WhyNJA@mail.gmail.com> In-Reply-To: <AE.74.17091.0A310E05@smtp01.insight.synacor.com> References: <AE.74.17091.0A310E05@smtp01.insight.synacor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30 Dec 2012 10:13, "Thomas Mueller" <mueller23@insightbb.com> wrote: > > > As the maintainer of devel/doxygen, I am trying to update the port to 1.8.3. > > But I am running into an error upon it trying to create it's docs. This > > appears to be due to the version of latex we use from teTeX being too old. > > > The problem is that it is failing on creating a .dvi version of the manual > > in order to create a .ps version of it. The creation of the .pdf version of > > the manual appears to be fine, but the creation of the other two appears to > > be specific to the FreeBSD port, and was being done prior to my taking over > > the port. > > > What I need to know is if there is actually a demand for the .dvi/.ps > > versions of the doxygen manual. I have been receiving some help from > > doxygen's developer, but considering that this problem isn't in an > > unmodified version of doxygen, I would prefer to stop supplying the .dvi/.ps > > files. > > > Thanks, > > Naram Qashat > > I think most modern printers handle .pdf files, and a package/port like xpdf > can read .pdf files without printing. I don't see .dvi/.ps files as useful, > more of a nuisance, but maybe some people have use for .dvi files with various > versions of TeX? Unless someone comes up with a good reason, I would leave them out. Anyone who is desperate for those files should have the skills to make them themselves. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839%2BMvBSt%2BN1zXKX44jOCPQ061bguNQ2NhX6TeK7WhyNJA>