* cus-load.el and loaddefs.el
@ 2002-03-20 20:27 Paul Michael Reilly
2002-03-20 20:56 ` Stefan Monnier
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Paul Michael Reilly @ 2002-03-20 20:27 UTC (permalink / raw)
Both of these files get generated at build time but are source
documents in CVS. Is this by design or should they be removed from
the source tree?
-pmr
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: cus-load.el and loaddefs.el
2002-03-20 20:27 cus-load.el and loaddefs.el Paul Michael Reilly
@ 2002-03-20 20:56 ` Stefan Monnier
2002-03-20 21:47 ` Andreas Schwab
2002-03-22 12:25 ` Richard Stallman
2 siblings, 0 replies; 8+ messages in thread
From: Stefan Monnier @ 2002-03-20 20:56 UTC (permalink / raw)
Cc: emacs-devel
> Both of these files get generated at build time but are source
> documents in CVS. Is this by design or should they be removed from
> the source tree?
They should ideally be removed but they are currently needed for
bootstrapping (at least loaddefs.el is, I think cus-load.el isn't).
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: cus-load.el and loaddefs.el
2002-03-20 20:27 cus-load.el and loaddefs.el Paul Michael Reilly
2002-03-20 20:56 ` Stefan Monnier
@ 2002-03-20 21:47 ` Andreas Schwab
2002-03-20 22:45 ` Paul Michael Reilly
2002-03-22 12:25 ` Richard Stallman
2 siblings, 1 reply; 8+ messages in thread
From: Andreas Schwab @ 2002-03-20 21:47 UTC (permalink / raw)
Cc: emacs-devel
Paul Michael Reilly <pmr@pajato.com> writes:
|> Both of these files get generated at build time but are source
|> documents in CVS. Is this by design or should they be removed from
|> the source tree?
You cannot bootstrap without loaddefs.el.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: cus-load.el and loaddefs.el
2002-03-20 21:47 ` Andreas Schwab
@ 2002-03-20 22:45 ` Paul Michael Reilly
2002-03-21 1:40 ` Stefan Monnier
0 siblings, 1 reply; 8+ messages in thread
From: Paul Michael Reilly @ 2002-03-20 22:45 UTC (permalink / raw)
Cc: emacs-devel
> Andreas Schwab writes:
>
> |> Both of these files get generated at build time but are source
> |> documents in CVS. Is this by design or should they be removed from
> |> the source tree?
>
> You cannot bootstrap without loaddefs.el.
Then I suppose we ought to create a file in CVS, say, loaddefs.el.src
(or some such) that gets copied to loaddefs.el at bootstrap time and
then gets populated subsequently. Then loaddefs.el and cus-load.el
can be removed from CVS. Any reason we should not do this?
It will eliminate conflicts that get reported by doing `cvs update'
and is probably cleaner.
-pmr
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: cus-load.el and loaddefs.el
2002-03-20 22:45 ` Paul Michael Reilly
@ 2002-03-21 1:40 ` Stefan Monnier
2002-03-21 6:03 ` Eli Zaretskii
2002-03-22 12:26 ` Richard Stallman
0 siblings, 2 replies; 8+ messages in thread
From: Stefan Monnier @ 2002-03-21 1:40 UTC (permalink / raw)
Cc: schwab, emacs-devel
>
> > Andreas Schwab writes:
> >
> > |> Both of these files get generated at build time but are source
> > |> documents in CVS. Is this by design or should they be removed from
> > |> the source tree?
> >
> > You cannot bootstrap without loaddefs.el.
>
> Then I suppose we ought to create a file in CVS, say, loaddefs.el.src
> (or some such) that gets copied to loaddefs.el at bootstrap time and
> then gets populated subsequently. Then loaddefs.el and cus-load.el
> can be removed from CVS. Any reason we should not do this?
Because I think it's better to just fix the bootstrapping problem
so that loaddefs.el is simply not needed any more.
I just haven't gotten the time to look into yet, although I know
it's not too difficult since I did get it to work a while back.
Stefan
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: cus-load.el and loaddefs.el
2002-03-21 1:40 ` Stefan Monnier
@ 2002-03-21 6:03 ` Eli Zaretskii
2002-03-22 12:26 ` Richard Stallman
1 sibling, 0 replies; 8+ messages in thread
From: Eli Zaretskii @ 2002-03-21 6:03 UTC (permalink / raw)
Cc: Paul Michael Reilly, schwab, emacs-devel
On Wed, 20 Mar 2002, Stefan Monnier wrote:
> Because I think it's better to just fix the bootstrapping problem
> so that loaddefs.el is simply not needed any more.
If this is done, there might be a need for a corresponding change to
make-dist, so that it would DTRT when a release tarball is prepared.
(I didn't try, so I don't know if the current make-dist will or will
not fail, I'm just making a remark for posterity.)
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: cus-load.el and loaddefs.el
2002-03-21 1:40 ` Stefan Monnier
2002-03-21 6:03 ` Eli Zaretskii
@ 2002-03-22 12:26 ` Richard Stallman
1 sibling, 0 replies; 8+ messages in thread
From: Richard Stallman @ 2002-03-22 12:26 UTC (permalink / raw)
Cc: pmr, schwab, emacs-devel
Without loaddefs.el, it would be necessary to scan all the .el files
for autoload cookies in order to build Emacs. That is likely to make
a considerable slowdown unless the scanning is done with a very
fast C program. To be reliable, that C program would need to
understand Lisp syntax as well as the Lisp reader does.
I am sure it could be done, but this change would be of no benefit to
users, so couldn't we spend the time doing one of the user-level tasks
in etc/TODO?
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: cus-load.el and loaddefs.el
2002-03-20 20:27 cus-load.el and loaddefs.el Paul Michael Reilly
2002-03-20 20:56 ` Stefan Monnier
2002-03-20 21:47 ` Andreas Schwab
@ 2002-03-22 12:25 ` Richard Stallman
2 siblings, 0 replies; 8+ messages in thread
From: Richard Stallman @ 2002-03-22 12:25 UTC (permalink / raw)
Cc: emacs-devel
Both of these files get generated at build time but are source
documents in CVS.
Building Emacs in the usual way does not generate these files.
It assumes they are present.
Please do not change this. Let's spend our time working on things
that will help users.
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2002-03-22 12:26 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-20 20:27 cus-load.el and loaddefs.el Paul Michael Reilly
2002-03-20 20:56 ` Stefan Monnier
2002-03-20 21:47 ` Andreas Schwab
2002-03-20 22:45 ` Paul Michael Reilly
2002-03-21 1:40 ` Stefan Monnier
2002-03-21 6:03 ` Eli Zaretskii
2002-03-22 12:26 ` Richard Stallman
2002-03-22 12:25 ` Richard Stallman
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).