Re: Shipping .texi sources in binary packages (was: unidentified subject)
Hi,
>>"Santiago" == Santiago Vila <sanvila@unex.es> writes:
Santiago> Some people propose that we ship .texi source in binary
Santiago> packages, but this means that we would have to identify
Santiago> *all* those extra files that are needed to generate the
Santiago> .html. This is a lot of (unneeded) work, IMHO.
Simple rule: ship all the *.texi{nfo} files. Not that hard to
do, I should think. Anyway, just looking at a makeinfo run pretty
much tells one what to ship.
Santiago> So shipping the .texi source will not be as easy as some
Santiago> people think,
And not as hard as some people think either. Frankly, any one
have problems identifying texi files should probably not be working
as a Debian developer. We do have quality standards, don't we?
Santiago> since there is not always a *single* file containing the
Santiago> "source".
So? This is a one time thing. Added the hint that the texinfo
files have a unique suffix, that does the identification for us,
partially.
Santiago> Sometimes there is even a Makefile to build the docs. Are
Santiago> we going to ship a Makefile too?
makeinfoo on the top level info file works quite well. There
is no need to ship the Makefile unless you so desire.
Santiago> It seems to me that the general rule that source belongs to
Santiago> the source package should apply here.
No. HTML is not a good format for printing. dvi files are not
quite as portable as one would like (due to font issues)
Santiago> We should already ship .html as this is our preferred
Santiago> documentation format (at least policy says so). Do we
Santiago> really need to make things more complex than they are now?
Yes. With SGML, I can choose plain text, HTML, tex,
postscript, or another SGML DTD. This is functionality that is not
crrently guaranteed.
Santiago> Why don't we concentrate instead in finding a standard
Santiago> procedure for registering html docs, our (already)
Santiago> preferred documentation format?
That too is a useful thing to have. So is an easy way of
generating nice, printable, documents. I should not have to download
the whole source just for a teeny .texi or .sgml file.
manoj
--
"Flint Paper is insane. I really respect that." Max
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: