unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: "Léo Le Bouter" <lle-bout@zaclys.net>, 47268@debbugs.gnu.org
Subject: [bug#47268] [PATCH v2 1/1] gnu: Add apostrophe.
Date: Fri, 19 Mar 2021 21:26:18 +0100	[thread overview]
Message-ID: <bad913a98986608579d298c8c83aeb3d92ff6908.camel@student.tugraz.at> (raw)
In-Reply-To: <20210319195849.19486-2-lle-bout@zaclys.net>

Am Freitag, den 19.03.2021, 20:58 +0100 schrieb Léo Le Bouter:
> +    (inputs
> +     `(("glib" ,glib)
> +       ("gobject-introspection" ,gobject-introspection)
> +       ("gspell" ,gspell)
> +       ("gtk+" ,gtk+)
> +       [...]
> +       ("webkitgtk" ,webkitgtk)
> +       ("js-mathjax" ,js-mathjax)))
Please try to keep the inputs sorted alphabetically.  Also, wouldn't we
need to wrap this somehow for it to be used?
> +    (native-inputs
> +     `(("gettext" ,gettext-minimal)
> +       ("glib:bin" ,glib "bin")
> +       ("pkg-config" ,pkg-config)))
> +    (home-page "https://gitlab.gnome.org/somas/apostrophe")
> +    (synopsis "Markdown editor written in Python with GTK+")
> +    (description "Apostrophe is a GTK+ based distraction free
> Markdown editor.
> +It uses pandoc as back-end for parsing Markdown.")
> +    (license (list license:gpl3
> +                   license:expat))))
We should probably add a comment, that Expat only applies to a single
source file.

Regards,
Leo






      reply	other threads:[~2021-03-19 20:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19 17:56 [bug#47268] [PATCH] gnu: Add apostrophe Leo Prikler
2021-03-19 19:58 ` [bug#47268] [PATCH v2 0/1] " Léo Le Bouter via Guix-patches via
2021-03-19 19:58   ` [bug#47268] [PATCH v2 1/1] " Léo Le Bouter via Guix-patches via
2021-03-19 20:26     ` Leo Prikler [this message]

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=bad913a98986608579d298c8c83aeb3d92ff6908.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=47268@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).