all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: VCSWITNESS = fail ** 2
Date: Sun, 12 Jan 2014 13:45:23 -0500	[thread overview]
Message-ID: <20140112184523.GC16457@thyrsus.com> (raw)
In-Reply-To: <8361pp84as.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org>:
> Actually, I take that back: the original code should work, and works
> for me.
> 
> So let's please step back one notch: can you please tell what exactly
> is wrong with the way vcswitness is computed and passed to the
> sub-Make?

What I know is this: 

I was trying to modify that code to DTRT in both a Bazaar and .git repo, 
using .git/HEAD as a witness in the latter case.  The way my modification 
failed caused me to suspect that the original code hadn't been working.

So I reverted to the trunk version and instrumented, by inserting an
echo before the generated make command.  Lo and behold, vcswitness was
empty.

I looked again.  Had I doubled $ properly for the make context?  I had;
vcswitness was really empty.  (But I was already pretty sure of that; if
doubling $$ had been incorrect it would have expanded as somebody's 
process number.)

I looked at those three lines again, saw the two different paths, and
made a deduction about the failure source that it now appears was 
incorrect.

But I've been around the track a few times, and I know that because 
of (a) conflicting Makefile and shell expansion rules  and (b) the
hair associated with nested Makefiles, this sort of code is notoriously
easy to misread (as Eli was later reminded himself).

So I posted to the list and waited for somebody to point out the flaw
in my reasoning.  Nobody did. Meanwhile, in my own test builds
vcswitness continued to be spuriously empty.

The rest you all know.  Eli took his own comic pratfall, momentarily
breaking the build. And he's been around the track a few times himself.

At present, I have no explanation for the observed differences in
behavior more predictive than "phase of the moon".

Those three lines are, by demonstration, so prone to be misread that they 
tripped up Eli and me in two different ways and I still have no theory
to account for why they were different.

That says "maintainence nightmare - should be scrapped and replaced"
to me.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>



  reply	other threads:[~2014-01-12 18:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 14:37 VCSWITNESS = fail ** 2 Eric S. Raymond
2014-01-12 15:02 ` 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 [this message]
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=20140112184523.GC16457@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=eliz@gnu.org \
    --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.