unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Léo Le Bouter via Guix-patches via" <guix-patches@gnu.org>
To: Xinglu Chen <public@yoctocell.xyz>, 47670@debbugs.gnu.org
Subject: [bug#47670] [PATCH 0/2] Add updater for packages hosted as SourceHut Git repositories
Date: Fri, 09 Apr 2021 14:04:48 +0200	[thread overview]
Message-ID: <2513bc7a1e52872be1cd1b8ecde11e21a6f613e0.camel@zaclys.net> (raw)
In-Reply-To: <87im4vwtyd.fsf@yoctocell.xyz>

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

On Fri, 2021-04-09 at 13:58 +0200, Xinglu Chen wrote:
> All the forges have different URL schemes so they would have to be
> hardcoded somehow, e.g. SourceHut uses
> https://git.sr.ht/~user/repo/archive/TAG.tar.gz, Gitea probably uses
> something else, etc..  Maybe we could just clone the repo, but that
> would use more bandwidth, and it could get pretty slow for big
> repositories.
> 

Is that an autogenerated tarball? I am under the impression that usage
of those is banned in GNU Guix, and that there's a lint pass for it.
What do you use these autogenerated tarballs for? Is the 'ls-remote'
command not enough to replace the version and hash? GNU Guix uses
shallow clones (AIUI) to save bandwidth, do you need this to generate
the hash? I encourage you use the same shallow clone mechanism here, so
it's more generic and not specific to Sourcehut.

> Adding a property for the tag prefix and suffix, and a version
> separator
> would be a good idea.  Right now it only supports "v" as a prefix and
> "_", ".", and "-" as separators.

What do you think about that last idea of matching versions in tags
with ANY separator and ANY suffix and prefix? That should work fine,
right? I can't think of a case where it wouldnt, but please do share
one if you do.

Thanks!!
Léo

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-04-09 12:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09  9:02 [bug#47670] [PATCH 0/2] Add updater for packages hosted as SourceHut Git repositories Xinglu Chen
2021-04-09  9:05 ` [bug#47670] [PATCH 1/2] upstream: Add predicate for Git URLs Xinglu Chen
2021-04-09  9:05 ` [bug#47670] [PATCH 2/2] gnu-maintenance: Add 'sourcehut-git' updater Xinglu Chen
2021-04-09 10:54 ` [bug#47670] [PATCH 0/2] Add updater for packages hosted as SourceHut Git repositories Léo Le Bouter via Guix-patches via
2021-04-09 11:58   ` Xinglu Chen
2021-04-09 12:04     ` Léo Le Bouter via Guix-patches via [this message]
2021-04-09 12:41       ` Xinglu Chen
2021-04-09 12:48         ` Xinglu Chen
2021-06-06 13:23           ` Ludovic Courtès
2021-06-11  9:25             ` Xinglu Chen
2021-07-27 10:19               ` Ludovic Courtès

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2513bc7a1e52872be1cd1b8ecde11e21a6f613e0.camel@zaclys.net \
    --to=guix-patches@gnu.org \
    --cc=47670@debbugs.gnu.org \
    --cc=lle-bout@zaclys.net \
    --cc=public@yoctocell.xyz \
    /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/guix.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).