unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Aurora via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: Guillaume Le Vaillant <glv@posteo.net>, 54268@debbugs.gnu.org
Subject: [bug#54268] [PATCH 5/6] gnu: Add cl-websocket-driver
Date: Wed, 09 Mar 2022 20:51:18 +0000	[thread overview]
Message-ID: <874k4697eh.fsf@disp3269> (raw)
In-Reply-To: <eefaccb5b5e60f823443835928cb19ea8bd071ea.camel@telenet.be>


Maxime Devos <maximedevos@telenet.be> writes:

> Guillaume Le Vaillant schreef op di 08-03-2022 om 18:52 [+0000]:
>> As far as I can see, the repository for websocket-driver doesn't have
>> any tag or release. Did you see a released version somewhere?
>
> In websocket-driver.asd, there's a line 0.2.0, suggesting the use
> of version numbers even if not tagged.  It's from commit
> <https://github.com/fukamachi/websocket-driver/commit/f97d3c39ae91a7b994315e740a93ef461c82e672>,
> which is seven year olds, though, so I guess that picking the latest
> commit from git instead would be reasonable.

Yeah, the lack of proper version tagging & the presence of versioning
info in the ASD project files are why I manually added the 0.2.0 while
using a commit.

I added the commit plus the version info because a number of changes
occured since it switched versions.

That author's projects tend to remain fairly stable once they're done
with them, but they don't tag them as 1.0 or anything.




  reply	other threads:[~2022-03-09 20:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06  3:33 [bug#54268] [PATCH 0/6] Add cl-clog and its missing dependencies Aurora via Guix-patches via
2022-03-06  3:33 ` [bug#54268] [PATCH 1/6] gnu: Add cl-template Aurora via Guix-patches via
2022-03-06  3:33 ` [bug#54268] [PATCH 2/6] gnu: Add cl-fast-websocket Aurora via Guix-patches via
2022-03-06  3:33 ` [bug#54268] [PATCH 3/6] gnu: Add cl-event-emitter Aurora via Guix-patches via
2022-03-06  3:33 ` [bug#54268] [PATCH 4/6] gnu: Add cl-sha1 Aurora via Guix-patches via
2022-03-06  3:33 ` [bug#54268] [PATCH 5/6] gnu: Add cl-websocket-driver Aurora via Guix-patches via
2022-03-08 18:35   ` Maxime Devos
2022-03-08 18:52     ` Guillaume Le Vaillant
2022-03-08 19:59       ` Maxime Devos
2022-03-09 20:51         ` Aurora via Guix-patches via [this message]
2022-03-06  3:33 ` [bug#54268] [PATCH 6/6] gnu: Add cl-clog Aurora via Guix-patches via
2022-03-08 18:29   ` Maxime Devos
2022-03-09 20:59     ` Aurora via Guix-patches via
     [not found] ` <handler.54268.B.164653763126451.ack@debbugs.gnu.org>
2022-03-06  3:55   ` [bug#54268] ([PATCH 0/6] Add cl-clog and its missing dependencies) Aurora via Guix-patches via
2022-03-08 13:19     ` [bug#54268] Add cl-clog and its missing dependencies Guillaume Le Vaillant

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=874k4697eh.fsf@disp3269 \
    --to=guix-patches@gnu.org \
    --cc=54268@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=maximedevos@telenet.be \
    --cc=rind38@disroot.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.savannah.gnu.org/cgit/guix.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).