Re: Contributing to Emacs Development

[Rob Browning]

Manoj Srivastava <address@hidden> writes:

>       Add to that a mechanism for building a dir file out of
>  snippets that programs can place in a directory, and debian can dump
>  its confusing install-info script that behave nothing like the
>  upstream install-info command (which debian does not need for its
>  packages). But that is a totally different wishlist ;-)

So where was this left?  Manoj, wrt Debian was there a policy ruling?

FWIW, Originally I tried "sedding" the info files to get the
cross-links right, this sort of worked, but was in general, BAD.
Eventually, some changes to info (can't recall if it was the
standalone one, or the emacs one) broke this approach.

After some fiddling around (and talking to people), I discovered the
fact that the info readers now tack the "current" dir onto INFOPATH,
and so I switched back to using the default upstream info files and
putting them in /usr/share/info/emacs-20/...  This appears to work
fairly well, but I suspect it does mean that cross-references from
other packages will be broken unless there are top-level symlinks in
/usr/share/info/.  I haven't released this package revision yet, but
it works better here than the current package.

WRT debian again, I spoke with Wichert, before I'd actually read this
thread, and he told me that he wants us to just quit using
install-info in Debian.  Instead, he's planning to rework doc-base to
automatically generate the dir file...

In any case, I'd just like to find out what the current concensus is,
if any, so I can release a new package that at least gets "info emacs"
right before Debian freezes.

Thanks

-- 
Rob Browning <address@hidden> PGP=E80E0D04F521A094 532B97F5D64E3930