From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: dana <dana@dana.is>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Posted zsh 5.9
Date: Sun, 15 May 2022 10:36:25 +0000 [thread overview]
Message-ID: <20220515103625.GC14994@tarpaulin.shahaf.local2> (raw)
In-Reply-To: <e8acb74d-d54a-42c4-a030-f6b798ddd6bb@www.fastmail.com>
dana wrote on Sat, May 14, 2022 at 18:50:13 -0500:
> On Sat 14 May 2022, at 18:26, Daniel Shahaf wrote:
> > I get "zsh-5.9.tar.xz.asc" with 1.20.1-1.1 (didn't test the other
> > version this time).
>
> Not sure then. It seems repeatable with the asc files for me here
>
I can reproduce it now, both with the 1.20.1-1.1 I used yesterday and
with 1.20.3-1ubuntu2 on a remote VM.
I haven't changed anything on my end.
As to workarounds, the committed one looks good, or we could specify the
filename explicitly by doing, say, «wget -O ${URL:h:t} $URL».
> On Sat 14 May 2022, at 18:28, Daniel Shahaf wrote:
> > Can't they install the man pages shipped in the source tarball in --HEAD
> > builds too?
>
> Yeah, that's what i was saying in the third paragraph you quoted. But that
> won't get them *all* the documentation like they have with bottles. They
> would have to pull both the source *and* doc archives to do that (since
> yodl is also needed to build the HTML files and those aren't included with
> the source). Which they might be fine with, idk; it would just be faster
> and more convenient if it was all in one place.
I don't understand the problem, since they'd _anyway_ have to get both
archives if they want to have HTML/PDF/info docs in --HEAD builds… but
more importantly, I think solving a problem before the user requirements
have been nailed down is putting the cart before the horse.
> I don't personally care about having local HTML documentation, though, and
> since SF only lets you have one 'latest' file (the source archive in our
> case) maybe adding man and run-help to the doc archive isn't that useful to
> Homebrew either.
If the lack of a single canonical URL to download the latest doc tarball
is a problem, we can solve that in a number of ways.
> I'll just see if they can pull the man pages from the 'latest' file
> with --HEAD
Sounds like a good next step. And they're welcome to file bug reports
against the distribution scheme :)
Cheers,
Dainel
next prev parent reply other threads:[~2022-05-15 10:37 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
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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220515103625.GC14994@tarpaulin.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--cc=zsh-workers@zsh.org \
/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.vuxu.org/mirror/zsh/
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).