From: Eli Zaretskii <eliz@gnu.org>
To: "Björn Bidar" <bjorn.bidar@thaodan.de>, "Po Lu" <luangruo@yahoo.com>
Cc: 74413@debbugs.gnu.org
Subject: bug#74413: [PATCH] Allow to store and read repository information of VCS builds
Date: Mon, 18 Nov 2024 14:45:27 +0200 [thread overview]
Message-ID: <86frnovhg8.fsf@gnu.org> (raw)
In-Reply-To: <87wmh1j6po.fsf@> (bug-gnu-emacs@gnu.org)
> Date: Mon, 18 Nov 2024 10:18:11 +0200
> From: Björn Bidar via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>
> Emacs has the feature to read the repository version and
> branch if git is installed during the build and afterwards if also
> the sources including the VCS repository is present.
>
> For the Android builds the feature was added to store and read the
> information mentioned above in a special version file.
Po Lu, why is that needed in the Android build, and how is it used
there?
> This patch reuses that mechanism so it can be reused on other platforms
> to use for the same reasons its available for Android and to also be
> able to use the information on CI workers without git installed and/or a
> full source checkout.
Doesn't that go against the tendency to have _less_ detailed/private
information in the build? We've lately removed some relatively useful
infos from what we report in commands that use the build information.
More generally, could you present the motivation and the rationale for
making this information available in production builds?
> The things I'm not sure about for this patch are:
> - Is the generating of the version file in the right place in
> Makefile.in
It should be in the build tree, yes.
> - Is the data directory the right place to store the file
Not sure, but I don't see why not.
> - Should the creation of the version file be shared between the Android
> builds and the other platforms
Let's first discuss whether this is at all needed and a good idea,
okay?
> - ${INSTALL_PROGRAM} $(INSTALL_STRIP) src/emacs${EXEEXT} "$(DESTDIR)${bindir}/$(EMACSFULL)"
> + ${INSTALL_PROGRAM} $(INSTALL_STRIP) src/emacs${EXEEXT} "$(DESTDIR)${bindir}/$(EMACS)"
Why this change (and other similar ones)? What does EMACSFULL have to
do with the repository version data?
> @@ -826,6 +837,7 @@ install-man:
> umask 022; ${MKDIR_P} "$(DESTDIR)${man1dir}"
> thisdir=`pwd -P`; \
> cd ${mansrcdir}; \
> + cp ctags.1 gnuctags.1; \
This hunk also looks unrelated.
next parent reply other threads:[~2024-11-18 12:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wmh1j6po.fsf@>
2024-11-18 12:45 ` Eli Zaretskii [this message]
2024-11-18 14:21 ` bug#74413: [PATCH] Allow to store and read repository information of VCS builds Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <875xoklj13.fsf@>
2024-11-18 14:55 ` Eli Zaretskii
2024-11-18 16:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87frnowkhp.fsf@>
2024-11-18 19:03 ` Eli Zaretskii
2024-11-18 19:31 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <874j44wd7k.fsf@>
2024-11-18 19:41 ` Eli Zaretskii
2024-11-18 21:48 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87y11g5i2x.fsf@>
2024-11-19 15:16 ` Eli Zaretskii
2024-11-19 16:13 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 17:08 ` Eli Zaretskii
2024-11-20 7:55 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-18 23:48 ` Stefan Kangas
2024-11-19 6:35 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 15:19 ` Eli Zaretskii
2024-11-19 16:16 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 17:20 ` Eli Zaretskii
2024-11-18 8:18 Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=86frnovhg8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74413@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=luangruo@yahoo.com \
/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).