lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: info files no longer built with `make all`


From: Jonas Hahnfeld
Subject: Re: info files no longer built with `make all`
Date: Fri, 07 Aug 2020 07:59:10 +0200
User-agent: Evolution 3.36.4

Am Freitag, den 07.08.2020, 00:11 +0200 schrieb Werner LEMBERG:
> >> The fix is incomplete, as I've just found out:

IMHO it would have been better to actually test the fix before
accepting and short-tracking it.

> >> `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 think that is because "STEPMAKE_TEMPLATES = texinfo" is no more.

> > 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.

I agree.

> 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.

It's not that !84 came out of nothing. It would have helped if people
actually tested before that landed, I was pretty much the only one...

Jonas

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]