Re: Can not make install

[Boris Shingarov]

> oh, also, "does it occur on make doc, or on make install" ?
 
Maybe that's just a missed dependency.  It occurs on "make install"
after a successful "make all".  The error message is this:
 
# make install
.. // bunch of successful stuff...
..
make[1]: Entering directory `/home/boris/lilypond/Documentation'
cp -p contributor.texi out/contributor.texi
export LILYPOND_DATADIR=
export
PYTHONPATH=/home/boris/lilypond/python/out:../python/auxiliar:/home/boris/lilypond/python/out:./python/auxiliar:
/usr/bin/python /home/boris/lilypond/stepmake/bin/install.py -c -d
/usr/local/share/info
install-info --remove --info-dir=/usr/local/share/info
./out/lilypond-usage.info ;  install-info --remove
--info-dir=/usr/local/share/info ./out/lilypond-changes.info ; 
install-info --remove --info-dir=/usr/local/share/info
./out/lilypond-contributor.info ;  install-info --remove
--info-dir=/usr/local/share/info ./out/lilypond-internals.info ; 
install-info --remove --info-dir=/usr/local/share/info
./out/lilypond-essay.info ;  install-info --remove
--info-dir=/usr/local/share/info ./out/lilypond-learning.info ; 
install-info --remove --info-dir=/usr/local/share/info
./out/lilypond-notation.info ;  install-info --remove
--info-dir=/usr/local/share/info ./out/music-glossary.info ; 
install-info --remove --info-dir=/usr/local/share/info
./out/lilypond-web.info ;  install-info --remove
--info-dir=/usr/local/share/info ./out/lilypond-extending.info ; true
install-info(./out/lilypond-usage.info): no entry for file `lilypond-usage'
install-info(./out/lilypond-changes.info): no entry for file
`lilypond-changes'
install-info(./out/lilypond-contributor.info): no entry for file
`lilypond-contributor'
install-info(./out/lilypond-internals.info): deleting entry `* LilyPond
Internals Reference: (lilypond-internals) ...'
install-info(./out/lilypond-essay.info): no entry for file `lilypond-essay'
install-info(./out/lilypond-learning.info): deleting entry `* LilyPond
Learning Manual: (lilypond-learning) ...'
install-info(./out/lilypond-notation.info): deleting entry `* LilyPond:
(lilypond-notation) ...'
install-info(./out/music-glossary.info): deleting entry `* Music
Glossary: (music-glossary) ...'
install-info(./out/lilypond-web.info): no entry for file `lilypond-web'
install-info(./out/lilypond-extending.info): no entry for file
`lilypond-extending'
install-info --info-dir=/usr/local/share/info ./out/lilypond-web.info

No `START-INFO-DIR-ENTRY' and no `This file documents'.
install-info(./out/lilypond-web.info): unable to determine description
for `dir' entry - giving up
make[1]: *** [local-install-info] Error 1
make[1]: Leaving directory `/home/boris/lilypond/Documentation'
make: *** [install] Error 2
#
 
Now, after that, invoking "make doc" results in building things I am
positive were not required for "install" before.
 
> I'm not particularly concerned if "make install"
> is broken with old libraries, since only package
> managers need to run that.
 
My end users run that.  I don't want to get into that old thread about
"release early" and "cathedral" stuff; but for me, your argument in
that thread was convincing because I see Lilypond as in some sense
similar to Debian, where "stable" means dynosaur bones.  I fix bugs
that my users are saying get in the way of their production work, and
implement and contribute back features that they need to continue their
production work.  I could base this work off the stable 2.12, but are
you willing to look at patches against 2.12's page-breaking code, which
is completely replaced in 2.13?  Therefore, I obviously must do
development against the latest master.  But the direction this
development is driven by my users; in fact, my patches get tested in
the field on production manuscripts before they even get uploaded on
appspot.  If "make install" is broken for users, this whole model of
development breaks down.
 
I wouldn't even care about this at all -- because I am not experiencing
this problem on my development machine -- if not the outcry of my users
who today can not use any of what I wrote in the past weeks.