Re: config.status has been broken by issue 5780 "Accept GUILE 2 without extra configure options"

[Werner LEMBERG]

>> and all of those messages are auto-generated.
> 
> So?  This does not provide a documented way of getting Guile
> activated at all unless you are a 14th level system building
> magician.

I'll try to update the documentation, too.

> So the correct way is to continue _heeding_ GUILE_CONFIG when it is
> given.

I suggest a deprecation warning like

  GUILE_CONFIG is no longer used.  Please use XXX instead.

> Is there anybody who recently built with a non-system version of
> Guile-1.8 intentionally?

I do this all the time.

> So please, can we stop pretending that anyone building LilyPond is a
> perfect omniscient programmer?

Usually, I try to insist on good documentation if people implement
stuff differently.  This time it slipped my attention that Han-Wen's
changes w.r.t. pkg-config are not properly described.


    Werner