From: phodina via Guix-patches via <guix-patches@gnu.org>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 51774@debbugs.gnu.org, "jlicht@fsfe.org" <jlicht@fsfe.org>
Subject: [bug#51774] [PATCH v2] gnu: font-adobe-source-code-pro: Update to 2.032R-ro-1.052R-it-1.012R-VAR.
Date: Wed, 17 Nov 2021 12:25:01 +0000 [thread overview]
Message-ID: <PVJZiPCokd0r9-WKLRiPuIZn4Mta51pS30tIMNzWgdf8uxNzI9k4QqoAIT020eHfAlZmGttBKif6rK3Y77Cult5hAz_QLeWgEFMQUtO9GqE=@protonmail.com> (raw)
In-Reply-To: <eaa8df516b60d38578d0ce9b95c3ac0b297eb189.camel@gmail.com>
Hi Liliana,
> This regexp could be simplified by noticing that it's always
>
> <VERSION>R-<TAG>/<VERSION>R-<TAG>/<VERSION>R-<TAG>, whereas we use
>
> <VERSION>R-<TAG>-<VERSION>R-<TAG>-<VERSION>R-<TAG>. So simply use a
>
> regexp that matches <VERSION>R-<TAG>- and then replace just the dash
>
> with a slash. That being said, I'm not sure how much cleaner this is
>
> compared to let-binding
>
> Cheers.
Thanks. I saw the pattern just I have issue writing down the regexp in Guile. Now you made me learn them properly :-D
* gnu/packages/fonts (font-adobe-source-code-pro): Update to
2.032R-ro-1.052R-it-1.012R-VAR and update regexp in commit.
diff --git a/gnu/packages/fonts.scm b/gnu/packages/fonts.scm
index 3f36a71bdd..c3ad57f203 100644
--- a/gnu/packages/fonts.scm
+++ b/gnu/packages/fonts.scm
@@ -975,7 +975,7 @@ (define-public font-hack
(define-public font-adobe-source-code-pro
(package
(name "font-adobe-source-code-pro")
- (version "2.030R-ro-1.050R-it")
+ (version "2.032R-ro-1.052R-it-1.012R-VAR")
(source
(origin
(method git-fetch)
@@ -984,10 +984,12 @@ (define-public font-adobe-source-code-pro
(commit (regexp-substitute/global
;; The upstream tag uses "/" between the roman and italic
;; versions, so substitute our "-" separator here.
- #f "R-ro-" version 'pre "R-ro/" 'post))))
+ #f "((R-ro)|(R-it))(-)" version
+ 'pre 1 "/" 'post
+ ))))
(file-name (git-file-name name version))
(sha256
- (base32 "0hc5kflr8xzqgdm0c3gbgb1paygznxmnivkylid69ipc7wnicx1n"))))
+ (base32 "1lqchm8z0ah5y675ycmciqvr8y1v1gcj22ysfs443gm291vy0z4v"))))
(build-system font-build-system)
(home-page "https://github.com/adobe-fonts/source-code-pro")
(synopsis
--
2.33.0
next prev parent reply other threads:[~2021-11-17 12:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 19:22 [bug#51774] [PATCH] gnu: Add font-source-code-pro phodina via Guix-patches via
2021-11-15 19:56 ` Liliana Marie Prikler
2021-11-15 22:12 ` phodina via Guix-patches via
2021-11-16 19:07 ` [bug#51774] [PATCH v2] gnu: font-adobe-source-code-pro: Update to 2.032R-ro-1.052R-it-1.012R-VAR phodina via Guix-patches via
2021-11-16 20:29 ` Liliana Marie Prikler
2021-11-17 12:25 ` phodina via Guix-patches via [this message]
2021-11-17 17:17 ` bug#51774: " Liliana Marie Prikler
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='PVJZiPCokd0r9-WKLRiPuIZn4Mta51pS30tIMNzWgdf8uxNzI9k4QqoAIT020eHfAlZmGttBKif6rK3Y77Cult5hAz_QLeWgEFMQUtO9GqE=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=51774@debbugs.gnu.org \
--cc=jlicht@fsfe.org \
--cc=liliana.prikler@gmail.com \
--cc=phodina@protonmail.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.