unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Mendler <mail@daniel-mendler.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] externals/marginalia 94fc7f0: README: Add ELPA badge
Date: Mon, 31 May 2021 15:18:37 +0200	[thread overview]
Message-ID: <f77cd6d3-040d-ddc2-f580-1c11c41b4374@daniel-mendler.de> (raw)
In-Reply-To: <2b8bd070-845e-6b73-3f1c-209c044b1c5d@daniel-mendler.de>

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

On 5/31/21 6:56 AM, Daniel Mendler wrote:
>> Would someone be interested in helping us make elpa.gnu.org serve those
>> "GNU ELPA badges" instead of asking shields.io to do it for us?
> 
> The shields.io code is available at https://github.com/badges/shields.
> It is of course possible to use that svg builder code during the ELPA
> build process. MELPA accesses shields.io during the build process, see
> https://github.com/melpa/melpa/blob/master/package-build/package-build-badges.el.

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.

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?

Daniel

[-- Attachment #2: badge.sh --]
[-- Type: application/x-sh, Size: 1962 bytes --]

  reply	other threads:[~2021-05-31 13:18 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 [this message]
2021-05-31 14:27         ` Stefan Monnier
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=f77cd6d3-040d-ddc2-f580-1c11c41b4374@daniel-mendler.de \
    --to=mail@daniel-mendler.de \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).