typically, when i install fedora, i install the above group since i
know that i'll be working with docbook and XML and so on. but it
seems that that group could stand some redefining, and possibly
refactoring into smaller bite-sized pieces.
here's the current definition:
Group: Authoring and Publishing
Description: These tools allow you to create documents in the DocBook
format and convert them into HTML, PDF, Postscript, and text.
Default Packages:
docbook-slides
docbook-style-dsssl
docbook-style-xsl
docbook-utils
docbook-utils-pdf
linuxdoc-tools
texlive
xhtml1-dtds
xmlto
Optional Packages:
BibTool
abcm2ps
conglomerate
dblatex
docbook2X
html401-dtds
kile
latex-mk
latexmk
lilypond
lout
ooo2txt
python-docutils
scribus
tetex-prosper
txt2rss
w3c-markup-validator
xdvik
xmlcopyeditor
Conditional Packages:
tex-cm-lgc
now that list is certainly not complete -- i just filed a bugzilla
request to add the packages "docbook5-schemas" and
"docbook5-style-xsl" since they seem to belong there. but there are a
lot of other packages that would seem to qualify as well if we're
talking about generating output formats from XML:
$ yum search fop
fop.noarch : XSL-driven print formatter
fop-javadoc.noarch : Javadoc for fop
...
$ yum search xalan
xalan-c.i586 : Xalan XSLT processor for C
xalan-c.x86_64 : Xalan XSLT processor for C
xalan-c-devel.i586 : Header files, libraries and development documentation for xalan-cxalan-c-devel.x86_64 : Header files, libraries and development
documentation for xalan-c
xalan-c-doc.x86_64 : Documentation for Xerces-C++ validating XML parser
xalan-j2.x86_64 : Java XSLT processor
xalan-j2-demo.x86_64 : Demo for xalan-j2
xalan-j2-javadoc.x86_64 : Javadoc for xalan-j2
xalan-j2-manual.x86_64 : Manual for xalan-j2
xalan-j2-xsltc.x86_64 : XSLT compiler
...
$ yum search saxon
saxon.noarch : Java XSLT processor
saxon-aelfred.noarch : Java XML parser
saxon-demo.noarch : Demos for saxon
saxon-javadoc.noarch : Javadoc for saxon
saxon-jdom.noarch : JDOM support for saxon
saxon-manual.noarch : Manual for saxon
saxon-scripts.noarch : Utility scripts for saxon
...
it seems only fair that the above packages belong in the "Authoring
and Publishing" group as well, no? and if "scribus" is there, surely
"publican" belongs, too.
on the flip side, some of that content could be removed, perhaps in
huge chunks. for instance, everything related to "tex" could be
broken out and placed in its own subgroup. AFAICT, tex is entirely
self-contained, is it not? so all tex-related packages could be
removed without affecting the rest.
in addition, there are packages that work strictly(?) with SGML
(docbook-utils, docbook-utils-pdf) and so may not be of much interest
to people dealing strictly with XML input.
anyway, you get the idea. that entire yum group looks a bit chaotic
and ill-defined, and it might not be out of line to have a breakdown
of everything related to that topic in smaller subgroups to pick and
choose just what you want.
thoughts?
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Linked In: http://www.linkedin.com/in/rpjday
Twitter: http://twitter.com/rpjday
========================================================================
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
