Hello,
There are packages that are shipped part of texlive, though texlive is not the upstream for those packages. Among those, some are in fedora texlive, as an exception because they were in tetex previously. I personally don't want to maintain them since I maintain enough packages already, but I can review them.
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
dvpdfm http://gaspra.kettering.edu/dvipdfm/
dvipng http://savannah.nongnu.org/projects/dvipng/
Not in fedora texlive but in upstream texlive: devnag http://devnag.sarovar.org/
detex http://www.cs.purdue.edu/homes/trinkle/detex/
ttf2pt1 http://ttf2pt1.sourceforge.net/
dvi2tty http://www.mesa.nl/pub/dvi2tty/
chktex
afm2pl http://tex.aanhet.net/afm2pl/
lcdf-typetools http://www.lcdf.org/type/
As a side note, dvipdfmx maybe should be packaged from the real upstream http://project.ktug.or.kr/dvipdfmx/ but it is not obvious since it is used in texlive.
-- Pat
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
On Sat, Jan 05, 2008 at 01:08:22PM +0000, Jonathan Underwood wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
No, the need for this would not disappear, at least for me.
-- Pat
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
On Sat, Jan 05, 2008 at 01:08:22PM +0000, Jonathan Underwood wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
No, the need for this would not disappear, at least for me.
Actually, yeah, having just done a local build of evince with the dvi backend enabled, I concur. There's some convenience issues for a start - evince still doesn't automatically reread a file when it changes on disk (which xdvi does), and there's something not working with source specials in evince as well.
On Sat, 2008-01-05 at 14:13 +0100, Patrice Dumas wrote:
On Sat, Jan 05, 2008 at 01:08:22PM +0000, Jonathan Underwood wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
No, the need for this would not disappear, at least for me.
But it's still a good idea.
Matthew Saltzman wrote, at 01/06/2008 01:52 AM +9:00:
On Sat, 2008-01-05 at 14:13 +0100, Patrice Dumas wrote:
On Sat, Jan 05, 2008 at 01:08:22PM +0000, Jonathan Underwood wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
No, the need for this would not disappear, at least for me.
But it's still a good idea.
pxdvi (in xdvi) is definitely needed for Japanese pTeX users.
Regards, Mamoru
On 05/01/2008, Mamoru Tasaka mtasaka@ioa.s.u-tokyo.ac.jp wrote:
pxdvi (in xdvi) is definitely needed for Japanese pTeX users.
Am in the process of hacking together a spec file for xdvi (including pxdvi) by hacking the relevant parts from the texlive SPEC. It doesn't build yet, but anyone feeling like helping can find it here:
On Sat, 2008-01-05 at 13:08 +0000, Jonathan Underwood wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
This has been enabled in rawhide for a while now.
On 05/01/2008, Matthias Clasen mclasen@redhat.com wrote:
On Sat, 2008-01-05 at 13:08 +0000, Jonathan Underwood wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
The need for this one would disappear if the evince packager would enable the dvi backend in evince (BZ #187381).
This has been enabled in rawhide for a while now.
So BZ #187381 can be closed RAWHIDE?
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
Hello,
There are packages that are shipped part of texlive, though texlive is not the upstream for those packages. Among those, some are in fedora texlive, as an exception because they were in tetex previously. I personally don't want to maintain them since I maintain enough packages already, but I can review them.
In texlive but should be separate: xdvik (xdvi) http://sourceforge.net/projects/xdvi
https://bugzilla.redhat.com/show_bug.cgi?id=427667
This package builds on F8, but still needs a fair bit of work, and is not yet review ready. However, I wanted to get it out in the open early to get feedback. Would welcome all and any hep.
What I have done: * Sun Jan 6 2008 Jonathan G. Underwood jonathan.underwood@gmail.com - 22.84.13-1 - Initial package based on the texlive.spec by Jindrich Novy - Updated to latest upstream xdvik and Japanese xdvik - Reviewed all patches relating to xdvi in texlive.spec and cherry picked those that are still needed - Reworked the patch to allow building of xdvik and pxdvik
What still needs to be done: Currently this builds against the bundled kpathsea library sources in the tarball. We should be building against the kpathsea(-devel) packages instead. Lots of missing Requires and BuildRequires. Needs building in Mock for devel and rpmlint checking. And testing lots.
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote:
Hello,
There are packages that are shipped part of texlive, though texlive is not the upstream for those packages. Among those, some are in fedora texlive, as an exception because they were in tetex previously. I personally don't want to maintain them since I maintain enough packages already, but I can review them.
In texlive but should be separate: dvpdfm http://gaspra.kettering.edu/dvipdfm/
[snip]
As a side note, dvipdfmx maybe should be packaged from the real upstream http://project.ktug.or.kr/dvipdfmx/ but it is not obvious since it is used in texlive.
On 05/01/2008, Patrice Dumas pertusus@free.fr wrote: [snip]
devel@lists.stg.fedoraproject.org
-
Jonathan Underwood -
Mamoru Tasaka -
Matthew Saltzman -
Matthias Clasen -
Patrice Dumas