From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] externals/marginalia 94fc7f0: README: Add ELPA badge
Date: Mon, 31 May 2021 10:27:56 -0400 [thread overview]
Message-ID: <jwvr1hnrnhv.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <f77cd6d3-040d-ddc2-f580-1c11c41b4374@daniel-mendler.de> (Daniel Mendler's message of "Mon, 31 May 2021 15:18:37 +0200")
> Stefan, I attached a "badge.sh" script which can be used to generate
> badges without depending on an external service. It uses imagemagick
> convert to compute the string width.
Thanks, that looks like just what we need.
> This script can be used as follows:
>
> ./badge.sh "GNU ELPA" "consult 0.8" bb3955 > consult.svg
> ./badge.sh "nonGNU ELPA" "markdown-mode 2.4" bb3955 > markdown-mode.svg
>
> Depending on how the ELPA build process works it may make more sense to
> convert this to an elisp script?
You can see the code we use at:
http://git.savannah.gnu.org/cgit/emacs/elpa.git/plain/elpa-admin.el?h=elpa-admin
In other words it's in the `elpa-admin.el` file in `elpa-admin` branch
of the `elpa.git` repository. So yes, using ELisp will make more sense.
So we'd want the badge URL used in the `README.(md|org)`s such that the
badge indicates the latest version of the package?
Stefan
next prev parent reply other threads:[~2021-05-31 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210530185719.10480.76043@vcs0.savannah.gnu.org>
[not found] ` <20210530185720.C7394209BF@vcs0.savannah.gnu.org>
2021-05-30 19:56 ` [elpa] externals/marginalia 94fc7f0: README: Add ELPA badge Stefan Monnier
2021-05-31 4:56 ` Daniel Mendler
2021-05-31 13:18 ` Daniel Mendler
2021-05-31 14:27 ` Stefan Monnier [this message]
2021-06-03 14:42 ` Basil L. Contovounesios
2021-06-03 14:51 ` Daniel Mendler
2021-06-03 15:16 ` Stefan Monnier
2021-06-03 16:07 ` Jean Louis
2021-06-03 23:12 ` chad
2021-06-09 20:54 ` Stefan Monnier
2021-06-09 21:41 ` Basil L. Contovounesios
2021-06-10 0:19 ` Jean Louis
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvr1hnrnhv.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=mail@daniel-mendler.de \
/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/emacs.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).