From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 52977@debbugs.gnu.org
Subject: [bug#52977] [PATCH 0/6] Update some minetest packages
Date: Tue, 11 Jan 2022 13:20:53 +0000 [thread overview]
Message-ID: <4ac31f9382a32aac6d633d642e4583afc184e020.camel@telenet.be> (raw)
In-Reply-To: <87fspuv3fg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Ludovic Courtès schreef op di 11-01-2022 om 13:53 [+0100]:
> Maxime Devos <maximedevos@telenet.be> skribis:
>
> > Ludovic Courtès schreef op wo 05-01-2022 om 23:30 [+0100]:
> > > > A TODO for the git-fetch updater:
> > > > * [ ] following redirects (to avoid mixed case -> lower case
> > > > changes
> > > > and .git suffixes in GitHub URLs)
> > > > * [ ] Support (let ((commit ...) (revision ...)) [...]) so more
> > > > packages can be updated automatically
> > >
> > > Hmm wasn’t it the reason we introduced ‘package-definition-location’?
> >
> > Yes, but it has been a while ago so I preferred to not overcomplicate
> > the patch series more.
>
> OK, I thought we more or less had a solution in place back then and just
> missed ‘package-definition-location’.
>
> I think we could do something along these lines:
>
> (edit-expression
> (location->source-properties (package-definition-location p))
> (lambda (str)
> ;; substitute commit ID in STR
> …))
>
> But yes, let’s keep that for a subsequent patch.
See <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53144>,
in particular the new 'latest-git' updater.
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-01-11 14:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 13:45 [bug#52977] [PATCH 0/6] Update some minetest packages Maxime Devos
2022-01-03 15:22 ` [bug#52977] [PATCH 1/6] gnu: minetest-basic-materials: Update to 2021-12-26 Maxime Devos
2022-01-03 15:22 ` [bug#52977] [PATCH 2/6] gnu: minetest-homedecor-modpack: " Maxime Devos
2022-01-03 15:22 ` [bug#52977] [PATCH 3/6] gnu: minetest-mobs: Update to 2021-12-12 Maxime Devos
2022-01-03 15:22 ` [bug#52977] [PATCH 4/6] gnu: minetest-mobs-animal: Update to 2021-11-14 Maxime Devos
2022-01-03 15:22 ` [bug#52977] [PATCH 5/6] gnu: minetest-technic: Update to 2021-09-11 Maxime Devos
2022-01-03 15:22 ` [bug#52977] [PATCH 6/6] gnu: minetest-unified-inventory: Update to 2021-12-26 Maxime Devos
2022-01-05 22:30 ` bug#52977: [PATCH 0/6] Update some minetest packages Ludovic Courtès
2022-01-05 23:18 ` [bug#52977] " Maxime Devos
2022-01-06 0:52 ` Liliana Marie Prikler
2022-01-06 9:33 ` Maxime Devos
2022-01-06 15:49 ` Liliana Marie Prikler
2022-01-11 12:53 ` Ludovic Courtès
2022-01-11 13:20 ` Maxime Devos [this message]
2022-01-05 23:21 ` Maxime Devos
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=4ac31f9382a32aac6d633d642e4583afc184e020.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=52977@debbugs.gnu.org \
--cc=ludo@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.