>> The fix is incomplete, as I've just found out: `make install`
>> doesn't install the info files. I looked a bit at the code but I
>> couldn't find out where the target is missing...
>
> I understand you personally want to build some info files quickly
> for browsing, but what use are info files without images to users
> that actually want to understand how to write music notation?
It *is* useful – for example for MacPorts – it's better to have
rudimentary documentation instead of none. David also gave a good
answer. I can imagine that users simply try to type `info lilypond`,
since it is a GNU program, and almost all GNU stuff comes with info
files. I absolutely see no reason to disable that.
It might sense to add a sentence to the headers of all 'naked'
LilyPond info files that for getting images you either have to do this
and that, or look at the corresponding PDF file.
BTW, had you mentioned that !84 removed 'naked' info handling, I
certainly would have noticed it earlier, and we could have discussed
that. Silently dropping this feature, however, is bad.
Werner
