help / color / mirror / code / Atom feed
From: dana <dana@dana.is>
To: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Cc: "Zsh hackers list" <zsh-workers@zsh.org>
Subject: Re: Posted zsh 5.9
Date: Sat, 14 May 2022 17:27:26 -0500	[thread overview]
Message-ID: <734c6a79-86c8-4e29-9f4e-6c2267626390@www.fastmail.com> (raw)
In-Reply-To: <20220514215010.GI13508@tarpaulin.shahaf.local2>

On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> For zsh.org there's little question where to put the keyring file, as
> there's only one relevant directory.  Any reason not to upload
> zsh-keyring.asc to zsh.org/pub?

That makes sense to me. I only didn't put it there because it wasn't there
before (and again creating-a-release isn't quite explicit about it). I've
added it now

On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> For me, «wget --content-disposition
> https://sourceforge.net/projects/zsh/files/zsh/5.9/zsh-5.9.tar.xz/download»
> DTRTs with both wget 1.20.1-1.1 and wget 1.21.3-1+b1 on Debian (buster
> and sid respectively).

That one works as expected for me as well, but try with
instead. For that one, with wget 1.21.3 from Homebrew, i get:

  Saving to: ‘zsh-5.9.tar.xz.asc?viasf=1’

Even though the headers contain:

  content-disposition: attachment; filename="zsh-5.9.tar.xz.asc"

On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> I think the man pages are there so yodl won't be a build dependency?
> I.e., so people who build from source but don't have yodl will still
> have man pages to install?

Right. Just wondering if they should also be in the doc archive, in case
someone wants to get all of the documentation in one place.

I had actually misread what Homebrew is doing btw. They pull the HTML files
from the doc archive *in addition to* installing the man pages from the
source one when you're using the bottle (not installing with --HEAD). So
there's no change needed for that.

However, when using --HEAD, they disable *all* documentation due to not
having yodl. If their policy allows it, they could pull at least the man
files out of https://sourceforge.net/projects/zsh/files/latest/download.
But if the doc archive additionally had the man and run-help files, they
could use that one archive to install *all* of the documentation (even if
it's a little outdated) even when building from source

On Sat 14 May 2022, at 16:50, Daniel Shahaf wrote:
> I hope workers/43692 didn't break this…

I checked the doc archive for 5.6.1, which was the last release before that
change, and it looks like it contains basically the same files as it does
now. And the man pages are still in the source archive as mentioned


  parent reply	other threads:[~2022-05-14 22:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-14 20:59 dana
2022-05-14 21:50 ` Daniel Shahaf
2022-05-14 21:58   ` Daniel Shahaf
2022-05-14 22:27   ` dana [this message]
2022-05-14 23:26     ` Daniel Shahaf
2022-05-14 23:28     ` Daniel Shahaf
2022-05-14 23:50       ` dana
2022-05-15 10:36         ` Daniel Shahaf
2022-05-15 21:43           ` dana
2022-05-16 23:57   ` Phil Pennock
2022-05-21  1:31     ` Daniel Shahaf
2022-05-14 22:11 ` Axel Beckert
2022-05-14 22:31   ` dana
2022-05-15  4:33     ` Bart Schaefer
2022-05-15  6:00       ` dana
2022-05-14 23:21   ` Daniel Shahaf
2022-05-14 23:35     ` Axel Beckert
2022-05-14 23:49       ` Daniel Shahaf

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=734c6a79-86c8-4e29-9f4e-6c2267626390@www.fastmail.com \
    --to=dana@dana.is \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \


* 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


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 NNTP newsgroup(s).