From: phillip.lord@russet.org.uk (Phillip Lord)
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: replacing ldefs-boot.el
Date: Tue, 29 Nov 2016 14:57:48 +0000 [thread overview]
Message-ID: <87k2bmgwpf.fsf@russet.org.uk> (raw)
In-Reply-To: <CAM-tV-_9dJLLw3rvCh8wRZimTWA1BtZPxYhzBkyAoM1QFQ1CgQ@mail.gmail.com> (Noam Postavsky's message of "Sun, 27 Nov 2016 18:04:24 -0500")
Noam Postavsky <npostavs@users.sourceforge.net> writes:
>> Actually, it should be *necessary* exactly as often as now. We need a
>> certain number of autoloads to bootstrap. Both ldefs-boot-auto and
>> ldefs-boot provide these. But ldefs-boot provides many more as well.
>
> Yes, and sometimes the extra ones that ldefs-boot provides could
> become necessary. In that case there wouldn't be a need to regenerate
> because they're already there. When using ldefs-boot-auto we would
> need to regenerate.
>
> Does that sound right?
Yes, that's true. This might occur, for example, if a file is re-ordered
so that a new function is hit first.
My suspision is that once we have a clear idea of the functions that are
used during bootstrap, this would happen rarely.
>>> Right. And I think the definitions you put would let make run them in
>>> parallel, thus breaking things.
>>
>>
>> bootstrap: | bootstrap-clean bootstrap-build
>>
>> ?
>
> I think it should be
>
> bootstrap: bootstrap-clean bootstrap-build
> boostrap-build: | bootstrap-clean
Ta!
Phil
next prev parent reply other threads:[~2016-11-29 14:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-20 17:46 replacing ldefs-boot.el Phillip Lord
2016-11-20 19:23 ` Eli Zaretskii
2016-11-20 21:28 ` Phillip Lord
2016-11-21 3:27 ` Eli Zaretskii
2016-11-21 22:03 ` Phillip Lord
2016-11-25 11:23 ` Phillip Lord
2016-11-25 13:28 ` Eli Zaretskii
2016-11-25 18:10 ` Paul Eggert
2016-11-25 19:31 ` Eli Zaretskii
2016-11-25 20:11 ` Stefan Monnier
2016-11-26 6:46 ` Eli Zaretskii
2016-11-26 12:08 ` Phillip Lord
2016-11-25 21:34 ` Phillip Lord
2016-11-25 23:18 ` Óscar Fuentes
2016-11-26 20:59 ` Phillip Lord
2016-11-27 20:14 ` Nicolas Petton
2016-11-25 21:11 ` Noam Postavsky
2016-11-25 21:57 ` Phillip Lord
2016-11-26 5:34 ` Noam Postavsky
2016-11-26 12:19 ` Phillip Lord
2016-11-27 23:04 ` Noam Postavsky
2016-11-29 14:57 ` Phillip Lord [this message]
2016-11-27 21:19 ` Phillip Lord
2016-12-13 12:17 ` Phillip Lord
2016-12-13 14:02 ` Noam Postavsky
2016-12-14 11:53 ` Phillip Lord
2016-12-13 14:58 ` John Wiegley
2016-12-13 16:08 ` Eli Zaretskii
2016-12-14 12:00 ` Phillip Lord
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=87k2bmgwpf.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).