From: Wolf <wolf@wolfsden.cz>
To: pukkamustard <pukkamustard@posteo.net>
Cc: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>,
"Guile User" <guile-user@gnu.org>
Subject: Re: [ANN] Guile SRFI-146 0.1.0 released (purely functional data structures)
Date: Sat, 12 Nov 2022 16:52:21 +0100 [thread overview]
Message-ID: <Y2/BNXeLqEYYEYvr@ws> (raw)
In-Reply-To: <86zgcw4obi.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On 2022-11-12 07:32:39 +0000, pukkamustard wrote:
>
> Hi,
>
> Aleix Conchillo Flaqué <aconchillo@gmail.com> writes:
>
> > Yes, I would also need guile-srfi-128. It would be great to have tarballs for each release. I was also trying to adding guile-eris, but
> > I was missing guile-sodium which unfortunately doesn't have a tarball. I believe you are also the maintainer of guile-sodium.
> >
> > Any chance we could get tarballs for those as well?
> >
> > Actually, if you had all projects in codeberg and created a tag (already creates tarballs) it would be even better and probably less
> > work for you.
I do not know about codeberg, but at least github does not guarantee
immutability of those auto-created archives. So they are annoying in any
context where you are checking checksums.
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-12 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:38 [ANN] Guile SRFI-146 0.1.0 released (purely functional data structures) pukkamustard
2022-08-08 17:27 ` Blake Shaw
2022-08-13 11:00 ` Linus Björnstam
2022-09-24 0:07 ` Aleix Conchillo Flaqué
2022-09-27 8:21 ` pukkamustard
2022-10-23 17:41 ` Aleix Conchillo Flaqué
2022-10-23 17:44 ` Aleix Conchillo Flaqué
2022-11-12 7:32 ` pukkamustard
2022-11-12 15:52 ` Wolf [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2/BNXeLqEYYEYvr@ws \
--to=wolf@wolfsden.cz \
--cc=aconchillo@gmail.com \
--cc=guile-user@gnu.org \
--cc=pukkamustard@posteo.net \
/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.
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).