GNU bug report logs -
#74413
[PATCH] Allow to store and read repository information of VCS builds
Previous Next
Reported by: Björn Bidar <bjorn.bidar <at> thaodan.de>
Date: Mon, 18 Nov 2024 08:19:02 UTC
Severity: wishlist
Tags: patch, wontfix
Done: Stefan Kangas <stefankangas <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> From: Björn Bidar <bjorn.bidar <at> thaodan.de>
> Cc: Stefan Kangas <stefankangas <at> gmail.com>, luangruo <at> yahoo.com,
> 74413 <at> debbugs.gnu.org
> Date: Mon, 18 Nov 2024 18:54:26 +0200
>
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
> > This is already available if Emacs is built in a Git repository, and
> > the information is stored in the dumped Emacs. So what is gained by
> > also recording the repository version on a disk file external to
> > Emacs?
>
> The information is only stored if the worker already had git installed
> and checked out the sources with git inside the worker.
> Also the function currently fails unless the system the user uses also happens to
> have git installed and the sources if the are installed also contain the
> VCS metadata.
> Storing the VCS metadata in the sources doesn't happen usually as it
> increases the size of a good chunk. In my case e.g. from 188MB to 788MB.
> Why not have the same feature for other platforms too?
Sorry, I don't understand this explanation; I'm probably missing
something.
The feature you propose requires to build Emacs inside a Git
repository, is that correct? Because otherwise "git rev-parse" will
not work, right? If that is correct, then building Emacs inside a Git
repository already calls this Git command and records the result in 2
Emacs Lisp variables. So why do you also want to record the same
information on a file? What kind of scenario do you have in mind in
which building Emacs with its current code will not record the branch
and the revision, but your additions to Makefile will record that?
This bug report was last modified 157 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.