From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: larsi@gnus.org, emacs-devel@gnu.org
Subject: Re: A target that's even more bootstrap?
Date: Tue, 18 Jun 2019 19:03:13 +0300 [thread overview]
Message-ID: <834l4mubi6.fsf@gnu.org> (raw)
In-Reply-To: <877e9jf429.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Tue, 18 Jun 2019 13:53:02 +0100
> Cc: emacs-devel@gnu.org
>
> mostlyclean
> clean
> distclean
> maintainer-clean
> extraclean
> bootstrap-clean
>
> The the irregular hyphenation is a bit odd.
clean, distclean, mostlyclean, and maintainer-clean are from the GNU
Coding Standards (GCS). Many projects have extraclean. So this is
tradition of sorts.
> But, in addition, I would guess that many of these levels
> (maintainer-clean, extraclean and bootstrap-clean) are really only
> there to save time; with parallel builds and faster machines I
> wonder how many of these are actually needed.
AFAIK, the issue at hand is not the speed, the issue is to know what
generated files get deleted. Some builds require a specific target
from this list to be run before the build. For example, if you weant
to reconfigure from scratch, you want distclean.
> If I understand it, distclean is most severe. So, why not ditch
> everything other than distclean and clean?
Because the GCS says otherwise?
next prev parent reply other threads:[~2019-06-18 16:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 11:22 A target that's even more bootstrap? Lars Ingebrigtsen
2019-06-18 12:16 ` Andreas Schwab
2019-06-18 12:27 ` Lars Ingebrigtsen
2019-06-18 12:53 ` Phillip Lord
2019-06-18 13:20 ` Stefan Monnier
2019-06-18 13:28 ` Lars Ingebrigtsen
2019-06-18 16:03 ` Eli Zaretskii [this message]
2019-06-19 9:29 ` Phillip Lord
2019-06-19 15:21 ` Eli Zaretskii
2019-06-19 13:15 ` Lars Ingebrigtsen
2019-06-19 14:00 ` Andreas Schwab
2019-06-19 15:28 ` Eli Zaretskii
2019-06-19 15:32 ` Lars Ingebrigtsen
2019-06-18 15:53 ` Eli Zaretskii
2019-06-18 15:58 ` Lars Ingebrigtsen
2019-06-18 16:54 ` Eli Zaretskii
2019-06-18 17:47 ` Andy Moreton
2019-06-18 19:22 ` Óscar Fuentes
2019-06-19 4:32 ` Elias Mårtenson
2019-06-19 5:29 ` Teemu Likonen
2019-06-19 15:12 ` Eli Zaretskii
2019-06-19 20:06 ` Juanma Barranquero
2019-06-19 20:19 ` Lars Ingebrigtsen
2019-06-19 20:26 ` Óscar Fuentes
2019-06-20 2:30 ` Eli Zaretskii
2019-06-19 11:53 ` Lars Ingebrigtsen
2019-06-19 12:33 ` Andy Moreton
2019-06-19 12:45 ` Óscar Fuentes
2019-06-19 13:35 ` Juanma Barranquero
2019-06-19 13:46 ` Lars Ingebrigtsen
2019-06-19 15:34 ` Eli Zaretskii
2019-06-19 15:43 ` Lars Ingebrigtsen
2019-06-19 15:48 ` Eli Zaretskii
2019-06-19 16:12 ` Lars Ingebrigtsen
2019-06-19 17:03 ` Eli Zaretskii
2019-06-19 17:29 ` Lars Ingebrigtsen
2019-06-19 18:18 ` Eli Zaretskii
2019-06-20 11:32 ` Lars Ingebrigtsen
2019-06-20 13:06 ` Eli Zaretskii
2019-06-20 14:23 ` Lars Ingebrigtsen
2019-06-20 15:10 ` Lars Ingebrigtsen
2019-06-20 16:29 ` Eli Zaretskii
2019-06-21 10:51 ` Lars Ingebrigtsen
2019-06-21 22:03 ` Paul Eggert
2019-06-23 2:48 ` Richard Stallman
2019-06-20 16:23 ` Eli Zaretskii
2019-06-20 16:27 ` Lars Ingebrigtsen
2019-06-20 16:46 ` Eli Zaretskii
2019-06-20 16:47 ` Lars Ingebrigtsen
2019-06-20 18:24 ` Paul Eggert
2019-06-19 15:29 ` Phillip Lord
2019-06-19 15:59 ` Óscar Fuentes
2019-06-19 16:18 ` Stefan Monnier
2019-06-19 16:35 ` Óscar Fuentes
2019-06-19 17:03 ` Out of tree builds [was Re: A target that's even more bootstrap?] Glenn Morris
2019-06-19 17:30 ` Óscar Fuentes
2019-06-19 17:13 ` A target that's even more bootstrap? Stefan Monnier
2019-06-19 17:43 ` Óscar Fuentes
2019-06-20 13:49 ` 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=834l4mubi6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=phillip.lord@russet.org.uk \
/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).