From: Christopher Baines <mail@cbaines.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 70971@debbugs.gnu.org, James Smith <jsubuntuxp@disroot.org>
Subject: [bug#70971] [PATCH v2 1/3] gnu: dhewm3: Use git repository.
Date: Sat, 22 Jun 2024 17:33:39 +0100 [thread overview]
Message-ID: <877ceh6ios.fsf@cbaines.net> (raw)
In-Reply-To: <864j9zzm00.fsf@disroot.org> (James Smith's message of "Tue, 11 Jun 2024 05:45:19 -0700")
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
James Smith <jsubuntuxp@disroot.org> writes:
> Christopher Baines <mail@cbaines.net> writes:
>
>> James Smith via Guix-patches via <guix-patches@gnu.org> writes:
>>
>>> * gnu/packages/game-development.scm (dhewm3) [source]: Use git repository
>>> instead of downloading a tarball from GitHub.
>>>
>>> Change-Id: I81ff5de0687221d7eec64b0165dbf10c2d041260
>>> ---
>>> gnu/packages/game-development.scm | 12 ++++++------
>>> 1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> I'm missing why you're making this change? I don't see anything wrong
>> with using these upstream release tarballs.
>
> I noticed that the package was using a tarball from GitHub and assumed
> that it was one that was autogenerated. Upon closer inspection, I see
> that it's a manually pack tarball instead. I can send a new set of
> patches that excludes switching to the git repository if needed.
I tried to apply the patches, but they look to have already been
applied.
I'll leave the issue open until it's been decided whether to keep the
switch to the Git repository or go back to using tarballs.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
next prev parent reply other threads:[~2024-06-22 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 0:42 [bug#70971] [PATCH 0/3] Update dhewm3 James Smith via Guix-patches via
2024-05-16 0:46 ` [bug#70971] [PATCH 1/3] gnu: dhewm3: Use git repository James Smith via Guix-patches via
2024-05-16 0:46 ` [bug#70971] [PATCH 2/3] gnu: dhewm3: Use gexps James Smith via Guix-patches via
2024-05-16 0:46 ` [bug#70971] [PATCH 3/3] gnu: dhewm3: Update to 1.5.3 James Smith via Guix-patches via
2024-06-07 5:45 ` [bug#70971] [PATCH v2 0/3] Update dhewm3 James Smith via Guix-patches via
2024-06-07 5:45 ` [bug#70971] [PATCH v2 1/3] gnu: dhewm3: Use git repository James Smith via Guix-patches via
2024-06-11 10:38 ` Christopher Baines
2024-06-11 12:45 ` James Smith via Guix-patches via
2024-06-22 16:33 ` Christopher Baines [this message]
2024-06-07 5:45 ` [bug#70971] [PATCH v2 2/3] gnu: dhewm3: Use gexps James Smith via Guix-patches via
2024-06-07 5:45 ` [bug#70971] [PATCH v2 3/3] gnu: dhewm3: Update to 1.5.3 James Smith via Guix-patches via
2024-06-30 10:46 ` bug#70971: Close Andreas Enge
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=877ceh6ios.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=70971@debbugs.gnu.org \
--cc=jsubuntuxp@disroot.org \
--cc=liliana.prikler@gmail.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 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.