From: esr@thyrsus.com (Eric S. Raymond)
To: emacs-devel@gnu.org
Subject: VCSWITNESS = fail ** 2
Date: Sun, 12 Jan 2014 09:37:33 -0500 (EST) [thread overview]
Message-ID: <20140112143733.B3F863811D4@snark.thyrsus.com> (raw)
Nobody has stepped up to own or defend this code in Makefile.in:
src: Makefile FRC
dirstate='.bzr/checkout/dirstate'; \
vcswitness='$$(srcdir)/../'$$dirstate; \
[ -r "$(srcdir)/$$dirstate" ] || vcswitness=''; \
cd $@ || exit; \
boot=bootstrap-emacs$(EXEEXT); \
[ ! -x "$$boot" ] || boot=''; \
$(MAKE) all $(MFLAGS) \
CC='${CC}' CFLAGS='${CFLAGS}' CPPFLAGS='${CPPFLAGS}' \
LDFLAGS='${LDFLAGS}' MAKE='${MAKE}' BOOTSTRAPEMACS="$$boot" \
VCSWITNESS="$$vcswitness"
Which is just as well, because the second through fourth lines
dirstate='.bzr/checkout/dirstate'; \
vcswitness='$$(srcdir)/../'$$dirstate; \
[ -r "$(srcdir)/$$dirstate" ] || vcswitness=''; \
are a case study in how not to do things. First, they're broken. The
readability test on line 4 is not checking the same file path that is
set on line 3. The contingent result with the current repo tree structure
is that vcswitness is never set. The necessary result under almost any
possible tree structure is that vcswitness would not be set correctly.
Now let's look at what VCSWITNESS is used for. The key lines are
in src/Makefile.in:
## VCSWITNESS points to the file that holds info about the current checkout.
## We use it as a heuristic to decide when to rebuild loaddefs.el.
## If empty it is ignored; the parent makefile can set it to some other value.
VCSWITNESS =
$(lispsource)/loaddefs.el: $(BOOTSTRAPEMACS) $(VCSWITNESS)
cd ../lisp; $(MAKE) $(MFLAGS) autoloads EMACS="$(bootstrap_exe)"
This test is wrong. The correct prerequisites would be every elisp
file that declares an autoload cookie. According to
find . -name '*.el' | xargs grep '#autoload' -l | wc -l
there are presently 786 such files. The right thing would be for
configure to generate that list into a makefile variable referenced
where VCSWITNESS is now.
I could find out who was responsible for this. I think I'd prefer not
to know, and to hope the person was basically competent but having a
bad day.
I'm going to delete the broken code. That will leave us no worse off,
and eliminate a Bazaar dependency. If I weren't eyeball-deep in
preparations for the git transition I'd actually fix this. But having
gone unnoticed for a long time suggests it's not very important. I'll
add an entry to BUGS or PROBLEMS.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
The difference between death and taxes is death doesn't get worse
every time Congress meets
-- Will Rogers
next reply other threads:[~2014-01-12 14:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 14:37 Eric S. Raymond [this message]
2014-01-12 15:02 ` VCSWITNESS = fail ** 2 Lars Magne Ingebrigtsen
2014-01-12 15:17 ` Eric S. Raymond
2014-01-12 17:28 ` Eli Zaretskii
2014-01-12 16:27 ` Eli Zaretskii
2014-01-12 16:45 ` Eric S. Raymond
2014-01-12 17:36 ` Eli Zaretskii
2014-01-12 18:04 ` Eli Zaretskii
2014-01-12 18:45 ` Eric S. Raymond
2014-01-12 18:53 ` Eli Zaretskii
2014-01-12 19:10 ` Glenn Morris
2014-01-12 21:00 ` Eli Zaretskii
2014-01-13 2:31 ` Glenn Morris
2014-01-12 19:25 ` David Kastrup
2014-01-12 19:42 ` Eric S. Raymond
2014-01-12 20:02 ` David Kastrup
2014-01-12 21:04 ` Eli Zaretskii
2014-01-13 15:41 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140112143733.B3F863811D4@snark.thyrsus.com \
--to=esr@thyrsus.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.