From: Xinglu Chen <public@yoctocell.xyz>
To: "Léo Le Bouter" <lle-bout@zaclys.net>, 47670@debbugs.gnu.org
Subject: [bug#47670] [PATCH 0/2] Add updater for packages hosted as SourceHut Git repositories
Date: Fri, 09 Apr 2021 13:58:18 +0200 [thread overview]
Message-ID: <87im4vwtyd.fsf@yoctocell.xyz> (raw)
In-Reply-To: <6b8ddedae2addf01efa57dcf3a6723bed81bf076.camel@zaclys.net>
On Fri, Apr 09 2021, Léo Le Bouter via Guix-patches via wrote:
> Thanks a lot for working on this!!
You are welcome. :)
> I have a question, why do you name it specific to Sourcehut? It could
> also work for Github, Gitlab, Gitea or Gogs etc., e.g.
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.
> Also I suggest adding a property to somehow specify what the version
> number format could be in tags, and also handling cases where format
> changes from version to version because upstream has not been
> consistent with naming. You can see for Hyperkitty they don't have the
> 'v' anymore starting 1.3.1, but I also have examples where version is
> separated by '_' and not '.', some times with prefix like:
> 'release_4_2_1', it would be nice to be able to specify those formats
> with e.g. regex and somehow also be able to handle inconsistency in
> upstream naming, maybe some heuristic to generically match version
> numbers separated by ANY character with any prefix or suffix?
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.
> Thank you!! :-D
Thank you for the feedback!
next prev parent reply other threads:[~2021-04-09 12:01 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 [this message]
2021-04-09 12:04 ` Léo Le Bouter via Guix-patches via
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=87im4vwtyd.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=47670@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
/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).