From: Greg Hogan <code@greghogan.com>
To: 73993@debbugs.gnu.org
Cc: Greg Hogan <code@greghogan.com>
Subject: [bug#73993] [PATCH v2 0/3] Pin git for git-sizer.
Date: Thu, 5 Dec 2024 21:04:30 +0000 [thread overview]
Message-ID: <cover.1733430615.git.code@greghogan.com> (raw)
In-Reply-To: <12475749a8d371488d9ae1fa331ad10dd24aa644.1729796653.git.code@greghogan.com>
The git package can be updated more readily if we reduce the number of
dependent packages. As in this patchset, we can depend on the pinned
version of git if we hard-code the location of the git executable and
do not propagate the dependency, which could cause profile conflicts.
The first patch fixes the issue where git was neither hard-coded nor
propagated and only worked because git is typically available in a user
profile. This can be tested with "guix shell --container git-sizer".
Greg Hogan (3):
gnu: git-sizer: Propagate git.
gnu: git-sizer: Use gexps.
gnu: git-sizer: Pin git version.
gnu/packages/version-control.scm | 44 +++++++++++++++++---------------
1 file changed, 24 insertions(+), 20 deletions(-)
base-commit: 006679d1e6ca7acea0629b4f019c8cf89cde08be
--
2.47.1
next prev parent reply other threads:[~2024-12-05 21:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 19:05 [bug#73993] [PATCH] gnu: git-sizer: Pin git version Greg Hogan
2024-11-29 9:40 ` Liliana Marie Prikler
2024-12-05 21:06 ` Greg Hogan
2024-12-05 21:04 ` Greg Hogan [this message]
2024-12-05 21:04 ` [bug#73993] [PATCH v2 1/3] gnu: git-sizer: Propagate git Greg Hogan
2024-12-18 11:02 ` Ludovic Courtès
2024-12-05 21:04 ` [bug#73993] [PATCH v2 2/3] gnu: git-sizer: Use gexps Greg Hogan
2024-12-18 11:03 ` Ludovic Courtès
2024-12-05 21:04 ` [bug#73993] [PATCH v2 3/3] gnu: git-sizer: Pin git version Greg Hogan
2024-12-06 21:19 ` Liliana Marie Prikler
2024-12-09 15:30 ` [bug#73993] [PATCH v3] " Greg Hogan
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1733430615.git.code@greghogan.com \
--to=code@greghogan.com \
--cc=73993@debbugs.gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.