Red Hat Bugzilla – Bug 178406
subpackage texi2dvi to avoid texinfo requiring tetex
Last modified: 2007-11-30 17:11:21 EST
Description of problem:
texinfo requires tetex which is rather a large package.
Most people only need makeinfo from texinfo, so would it be possible
to separate texi2dvi to a separate subpackage (texi2dvi?) so that
installing makeinfo would not installing the whole of tetex?
Unfortunately there's AFAIK no clean way to split a package and make sure both
parts are installed after an upgrade. Considering that the "average developer"
(I know...) will need tetex at least for docbook-utils/xmlto, I don't think it is
worth the trouble.
I was just going to file a bug with the same request when I found this. Let me
just give an example of where splitting this would help. All of the online help
in octave is texinfo formatted and so octave requires makeinfo. This means that
to install octave, you must install tetex, which means tetex-fonts as well. The
rpms for octave and a few library dependencies are a total of 10-20 MB (I don't
remember the total). The rpms for tetex and tetex-fonts are a total of 42 MB,
more than twice the size of everything else to be installed.
Fair point, let's do it for FC6.
Fixed in rawhide texinfo-4.8-11. Thanks for your report.
Re-opening bug to request FC-4 and FC-5 package update.
The package splitting broke at least one build requirement list of a Fedora
Extras package that I maintain. The package in question - asymptote -requires
the file texi2dvi to create the main pdf doc file.
In order to avoid having different specfiles for the FC-4/FC-5, and devel (FC-6)
branches I would like to request an update of the FC-4 and FC-5 texinfo package
that would also provide the texinfo-tex package (Provides: texinfo-tex).
Thanks in advance,
PS - I know I could build require the file /usr/bin/texi2dvi but upstream just
warned yesterday that it needs a particular version of the above file to
successfully build the pdf file.
Changing the package list within a release can break kickstarts or make tested
and documented processes invalid. I don't think inconveniencing all our users
to make single developer's task somewhat easier is worth it.
(In reply to comment #6)
> Changing the package list within a release can break kickstarts or make tested
> and documented processes invalid.
I have not requested the splitting of the FC-4 and FC-5 texinfo package, I only
suggested the addition of a provides statement to the FC-4 and FC-5 packages
specfiles. AFAICT that will not change the FC-4/FC-5 package list.
I'm sorry, I wasn't paying enough attention. Adding a provides: is reasonable.
texinfo-4.8-9.2.fc5.1 has been pushed for fc5, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
Both packages should be pushed now.
Thanks for the FC-4 and FC-5 updates.