From: "Ludovic Courtès" <ludo@gnu.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 38436@debbugs.gnu.org
Subject: [bug#38436] [PATCH] gnu: Add gfortran-toolchain
Date: Wed, 11 Dec 2019 12:12:04 +0100 [thread overview]
Message-ID: <87y2vjjeuz.fsf@gnu.org> (raw)
In-Reply-To: <m1zhfzgnn5.fsf@fastmail.net> (Konrad Hinsen's message of "Wed, 11 Dec 2019 11:30:38 +0100")
Hi Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> * gnu/packages/commencement.scm: (gfortran-toolchain): New variable.
> * gnu/packages/commencement.scm: (make-gcc-toolchain): Added argument "language"
We’re almost there. :-)
> +;; The synopsis and description must be literal strings (not constructed
> +;; using string-append or format) to make them translatable.
> +(define gcc-synopsis
> + "Complete GCC tool chain for C/C++ development")
> +(define gcc-description
> + "This package provides a complete GCC tool chain for C/C++ development to
> +be installed in user profiles. This includes GCC, as well as libc (headers
> +and binaries, plus debugging symbols in the @code{debug} output), and
> +binutils.")
>
> (define* (make-gcc-toolchain gcc
> - #:optional
> - (libc #f))
> - "Return a complete toolchain for GCC. If LIBC is specified, target that libc."
> + #:optional
> + (synopsis gcc-synopsis)
> + (description gcc-description)
xgettext recognizes (synopsis "foo"), but it won’t catch the variables
defined above, because they’re not preceded by the ‘synopsis’ keyword or
anything.
That’s why I proposed in <https://issues.guix.gnu.org/issue/38436#2> to
arrange to keep the string wrapped in (synopsis …).
It’d be great if you could give it a spin, or I can make the change on
your behalf if you prefer.
Apologies for making something simple somewhat complicated!
Thanks,
Ludo’.
next prev parent reply other threads:[~2019-12-11 13:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 17:46 [bug#38436] [PATCH] gnu; Add gfortran-toolchain Konrad Hinsen
2019-12-02 15:01 ` [bug#38436] [PATCH] gnu: " Konrad Hinsen
2019-12-09 14:30 ` Ludovic Courtès
2019-12-10 13:11 ` Konrad Hinsen
2019-12-10 14:38 ` Ludovic Courtès
2019-12-11 10:30 ` Konrad Hinsen
2019-12-11 10:30 ` Konrad Hinsen
2019-12-11 11:12 ` Ludovic Courtès [this message]
2019-12-11 20:34 ` Konrad Hinsen
2019-12-12 13:20 ` Ludovic Courtès
2019-12-12 15:19 ` Konrad Hinsen
2019-12-12 21:22 ` Ludovic Courtès
2019-12-13 12:56 ` Konrad Hinsen
2019-12-13 12:53 ` Konrad Hinsen
2019-12-13 12:56 ` Jonathan Brielmaier
2019-12-14 23:22 ` bug#38436: " 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=87y2vjjeuz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38436@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.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).