From: David Kastrup <dak@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Witness computation - minor breakage in the build system
Date: Sun, 12 Jan 2014 21:07:03 +0100 [thread overview]
Message-ID: <874n59c6c8.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87r48dgeo4.fsf@igel.home> (Andreas Schwab's message of "Sun, 12 Jan 2014 20:53:31 +0100")
Andreas Schwab <schwab@linux-m68k.org> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>
>>>> The benefit is that a deoendency on the VCS goes away.
>>>
>>> I don't see that should be considered as a benefit.
>>
>> Well, the whole point of the GPL and the delivered source tar balls is
>> to give the user the ability to make his own changes. If the Makefile
>> dependencies don't work when making changes to the source from a
>> tarball, it does not look much like a source tarball.
>
> I don't think you can put that much into it. You can alway run `make -C
> lisp autoloads' manually to update loaddefs.el.
Is that documented anywhere? "You can always" is adequate justification
for not including any build script, since you can always execute all
steps manually. If there is no reasonably discoverable way of what one
can always do, it seems somewhat theoretic.
The usual expectation is that modifying files will let "make" rebuild
what is necessary.
--
David Kastrup
next prev parent reply other threads:[~2014-01-12 20:07 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-12 4:37 Witness computation - minor breakage in the build system Eric S. Raymond
2014-01-12 4:50 ` Paul Eggert
2014-01-12 5:08 ` Eric S. Raymond
2014-01-12 14:52 ` Stefan Monnier
2014-01-12 14:57 ` Eric S. Raymond
2014-01-12 19:36 ` Stefan Monnier
2014-01-12 19:45 ` David Kastrup
2014-01-12 19:53 ` Andreas Schwab
2014-01-12 20:07 ` David Kastrup [this message]
2014-01-12 15:57 ` Eli Zaretskii
2014-01-12 14:51 ` Stefan Monnier
2014-01-12 15:56 ` Eli Zaretskii
2014-01-12 19:22 ` Paul Eggert
2014-01-12 19:43 ` Eric S. Raymond
2014-01-12 22:29 ` Stefan Monnier
2014-01-12 22:51 ` Paul Eggert
2014-01-13 3:14 ` Stefan Monnier
2014-01-13 3:44 ` Paul Eggert
2014-01-13 4:16 ` Stefan Monnier
2014-01-13 6:27 ` Paul Eggert
2014-01-13 14:06 ` Stefan Monnier
2014-01-12 21:01 ` Eli Zaretskii
2014-01-12 19:15 ` Glenn Morris
2014-01-13 3:16 ` Glenn Morris
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874n59c6c8.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).