emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Updating autoloads, custom-deps, finder-data


From: Glenn Morris
Subject: Re: Updating autoloads, custom-deps, finder-data
Date: Sat, 20 Apr 2013 13:58:10 -0400
User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)

Eli Zaretskii wrote:

> Btw, I did see this comment in lisp/Makefile.in:
>
>   # custom-deps and finder-data both used to scan _all_ the *.el files.
>   # This could lead to problems in parallel builds if automatically
>   # generated *.el files (eg loaddefs etc) were being changed at the same 
> time.
>   # One solution was to add autoloads as a prerequisite:
>   # http://lists.gnu.org/archive/html/emacs-pretest-bug/2007-01/msg00469.html
>   # http://lists.gnu.org/archive/html/bug-gnu-emacs/2007-12/msg00171.html
>   # However, this meant that running these targets modified loaddefs.el,
>   # every time (due to time-stamping).  Calling these rules from
>   # bootstrap-after would modify loaddefs after src/emacs, resulting
>   # in make install remaking src/emacs for no real reason:
>   # http://lists.gnu.org/archive/html/emacs-devel/2008-02/msg00311.html
>   # Nowadays these commands don't scan automatically generated files,
>   # since they will never contain any useful information
>   # (see finder-no-scan-regexp and custom-dependencies-no-scan-regexp).
>
> but it is unclear to me what's its conclusion.  Problems with parallel
> builds can be taken care of by proper dependencies and/or by judicial
> use of temporary files and move-if-change.  And the last sentence
> seems to say that at least some of the problems no longer exist(?)
>
> IOW, the status of this issue is unclear.

Seems clear to me, but I think I wrote it.
The stuff in the past tense describes the problems that used to exist.
The stuff in the present tense describes why they don't exist now.

(I don't recall if there is an issue with _versioned_ files that contain
autoload information, eg rmail.el. In practice I have never seen one.)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]