From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Daniel Mendler <mail@daniel-mendler.de>, emacs-devel@gnu.org
Subject: Re: [elpa] externals/marginalia 94fc7f0: README: Add ELPA badge
Date: Thu, 03 Jun 2021 15:42:44 +0100 [thread overview]
Message-ID: <87im2vovq3.fsf@tcd.ie> (raw)
In-Reply-To: <jwvr1hnrnhv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 31 May 2021 10:27:56 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 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?
Yes, and thanks for setting up this nice eye candy.
Only minor issue is that the new badges don't play well with hosting
services that aggressively cache images, such as GitHub:
https://github.com/magnars/dash.el
Note that the GNU-devel ELPA version trails the corresponding MELPA one
due to server-side caching.
MELPA seems to solve this by configuring their NGINX web server to serve
badges with the HTTP header 'Cache-Control: no-cache':
https://github.com/melpa/melpa/pull/2231
https://github.com/melpa/melpa/commit/d75f22a6
https://github.com/melpa/melpa/commit/1834069f
$ wget -Sq https://elpa.gnu.org/devel/dash.svg
HTTP/1.1 200 OK
Date: Thu, 03 Jun 2021 14:27:49 GMT
Server: Apache/2.4.38 (Debian)
Last-Modified: Wed, 02 Jun 2021 21:02:33 GMT
ETag: "522-5c3cec70ecf29"
Accept-Ranges: bytes
Content-Length: 1314
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive
Content-Type: image/svg+xml
$ wget -Sq https://melpa.org/packages/dash-badge.svg
HTTP/1.1 200 OK
Server: nginx
Date: Thu, 03 Jun 2021 14:28:05 GMT
Content-Type: image/svg+xml
Content-Length: 1165
Last-Modified: Thu, 03 Jun 2021 13:27:58 GMT
Connection: keep-alive
ETag: "60b8d8de-48d"
Cache-Control: no-cache
Accept-Ranges: bytes
Is there someone here with access to GNU ELPA's Apache configuration
that would make a similar change? If not, where should this request go?
Thanks,
--
Basil
next prev parent reply other threads:[~2021-06-03 14:42 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
2021-06-03 14:42 ` Basil L. Contovounesios [this message]
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=87im2vovq3.fsf@tcd.ie \
--to=contovob@tcd.ie \
--cc=emacs-devel@gnu.org \
--cc=mail@daniel-mendler.de \
--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).