From: Mike Gran <spk121@yahoo.com>
To: Bug Guile <bug-guile@gnu.org>
Subject: guile.m4 may need serial number
Date: Thu, 27 Dec 2007 08:39:52 -0800 (PST) [thread overview]
Message-ID: <209323.8795.qm@web37902.mail.mud.yahoo.com> (raw)
The automake manual recommends that .m4 files use a serial number for versioning, so that it is possible to tell when an .m4 installed by aclocal is updated.
<quote>
Because third-party macros defined in ‘*.m4’ files are naturally shared between multiple
projects, some people like to version them. This makes it easier to tell which of two M4
files is newer. Since at least 1996, the tradition is to use a ‘#serial’ line for this.
A serial number should be a single line of the form
# serial version
where version is a version number containing only digits and dots. Usually people use a
single integer, and they increment it each time they change the macro (hence the name of
“serial”). Such a line should appear in the M4 file before any macro definition.
The ‘#’ must be the first character on the line, and it is OK to have extra words after
the version, as in
#serial version garbage
Normally these serial numbers are completely ignored by aclocal and autoconf, like
any genuine comment. However when using aclocal’s ‘--install’ feature, these serial
numbers will modify the way aclocal selects the macros to install in the package: if two
files with the same basename exists in your search path, and if at least one of them use a
‘#serial’ line, aclocal will ignore the file that has the older ‘#serial’ line (or the file that
has none).
</quote>
Thanks,
Mike Gran
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2007-12-27 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 16:39 Mike Gran [this message]
2007-12-30 11:11 ` guile.m4 may need serial number Neil Jerram
-- strict thread matches above, loose matches on Subject: below --
2007-12-30 16:08 Mike Gran
2008-01-01 19:13 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=209323.8795.qm@web37902.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=bug-guile@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).