unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jérôme Marant" <jmarant@free.fr>
Cc: emacs-devel@gnu.org
Subject: Re: [PATCH] make-dist fixes and clean-ups
Date: Tue, 10 May 2005 11:42:47 +0200	[thread overview]
Message-ID: <1115718167.42808217a86b9@imp5-q.free.fr> (raw)
In-Reply-To: <874qdb4huc.fsf@xs4all.nl>

Quoting Lute Kamstra <Lute.Kamstra.lists@xs4all.nl>:

> > Many people already proposed that
>
> Huh?  I didn't see it in any of the messages posted to emacs-devel.
> They all talked about changing Emacs' Makefiles or the Debian script,
> not about changing make-dist.

Sorry, you're right, it was proposed to do so out of make-dist,
but it was the same idea.

> > but this is wrong since 'make maintainer-clean', which undoes the
> > bootstrap, will remove loaddefs.el (which is fine since
> > autogenerated files have to be removed).
> >
> > Hence, I can't bootstrap more than once with the same tarball.
>
> Out of curiosity: do you have any special reason to do a "make
> maintainer-clean" before a second "make bootstrap"?  Why do a second
> bootstrap at all?

Yes, I do. I do build a package from within the unpacked tarball,
and when I do many attempts, make bootstrap and make maintainer-clean
are run on the same tree many times: not to have to unpack the same
tree at every attempt is handy.

> > How about leaving ldefs-boot.el and see if it hurts?
>
> Apart from being redundant under normal circumstances, it probably
> doesn't hurt in any way.  Come to think of it: it's actually a nice
> feature that the distribution tarball allows a "make maintainer-clean"
> and then a ".configure" plus "make bootstrap".

Indeed.

> You convinced me to distribute ldefs-boot.el.  ;-)

I'm glad I did :-)

Thanks.

--
Jérôme Marant

  reply	other threads:[~2005-05-10  9:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-30 11:04 [PATCH] make-dist fixes and clean-ups Jérôme Marant
2005-05-01 12:06 ` Lute Kamstra
2005-05-01 12:18   ` Jérôme Marant
2005-05-01 15:12     ` Stefan Monnier
2005-05-01 17:10       ` Jérôme Marant
2005-05-01 19:58         ` Kim F. Storm
2005-05-01 20:19           ` Jérôme Marant
2005-05-01 22:35             ` Thien-Thi Nguyen
2005-05-02  7:32               ` Jérôme Marant
2005-05-02 22:33                 ` Thien-Thi Nguyen
2005-05-02 23:41                 ` Richard Stallman
2005-05-02  9:59             ` Kim F. Storm
2005-05-02 11:54               ` Jérôme Marant
2005-05-01 23:39         ` Richard Stallman
2005-05-02  6:51           ` Jérôme Marant
2005-05-09 12:19     ` Lute Kamstra
2005-05-09 22:57       ` Jérôme Marant
2005-05-10  8:15         ` Lute Kamstra
2005-05-10  9:42           ` Jérôme Marant [this message]
2005-05-10  9:04       ` Richard Stallman
2005-05-10 15:11         ` Lute Kamstra
2005-05-11 16:27           ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2005-04-30  9:55 Jérôme Marant

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=1115718167.42808217a86b9@imp5-q.free.fr \
    --to=jmarant@free.fr \
    --cc=emacs-devel@gnu.org \
    --cc=jerome.marant@free.fr \
    /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).