|
From: | Auto mailings of changes to Lily Issues via Testlilyissues-auto |
Subject: | [Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5831 Modularize `aclocal.m4` |
Date: | Sat, 07 Mar 2020 10:07:14 -0000 |
[issues:#5831] Modularize aclocal.m4
Status: New
Created: Sat Mar 07, 2020 10:07 AM UTC by Werner LEMBERG
Last Updated: Sat Mar 07, 2020 10:07 AM UTC
Owner: nobody
In standard GNU projects, the aclocal.m4
file gets auto-generated with the aclocal
script; the necessary M4 scripts are either taken from the system or from a directory that gets specified with some
command line options to aclocal
.
Looking into the git history of LilyPond's aclocal.m4
file I can see that this was true in the very beginning. However, later on people started to modify this file manually. Was this intentional?
I suggest to use aclocal
again, modularizing the current stuff in aclocal.m4
by splitting it into various .m4
files in a m4
top-level subdirectory.
Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Prev in Thread] | Current Thread | [Next in Thread] |