emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#57744: closed ([PATCH 0/3] Add shirah and dependencies)


From: GNU bug Tracking System
Subject: bug#57744: closed ([PATCH 0/3] Add shirah and dependencies)
Date: Fri, 16 Sep 2022 10:45:02 +0000

Your message dated Fri, 16 Sep 2022 12:43:27 +0200
with message-id <87bkrfsio9.fsf@cbaines.net>
and subject line Re: [bug#57744] [PATCH v3 3/3] gnu: Add shirah.
has caused the debbugs.gnu.org bug report #57744,
regarding [PATCH 0/3] Add shirah and dependencies
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
57744: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57744
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: [PATCH 0/3] Add shirah and dependencies Date: Mon, 12 Sep 2022 02:09:15 +0200
shirah is a terminal-based ebook reader, which alone I'd see as a nice addition 
to Guix packages considering how light, flexible and customizable (themes, 
opacity, font options, keybindings) terminal emulators are, but it also comes 
with an optional RSVP mode for speed reading, which can be pretty convenient 
for a terminal reader since terminal windows can be resized to very small 
geometry without breaking. shirah also supports basic ebook-reading features, 
like resuming a read, or browsing from the TOC.

M (3):
  gnu: Add python-ebooklib.
  gnu: Add python-syllables.
  gnu: Add shirah.

 gnu/packages/ebook.scm      | 40 +++++++++++++++++++++++++++++++++++++
 gnu/packages/python-xyz.scm | 20 +++++++++++++++++++
 2 files changed, 60 insertions(+)

-- 
2.37.2




--- End Message ---
--- Begin Message --- Subject: Re: [bug#57744] [PATCH v3 3/3] gnu: Add shirah. Date: Fri, 16 Sep 2022 12:43:27 +0200 User-agent: mu4e 1.8.9; emacs 28.1
Mathieu <matf@disr.it> writes:

> Thanks for clarifying! Shirah does not include a license file indeed,
> but the end of the README clarifies the intent of the author: they say
> we can use gpl2 or any later version at our convenience. "gpl2+"
> indeed looks more relevant then since it is listed in one of the
> source files, as you found.
>
> Hopefully the patchset v3 is okay (I had to reset and restart from
> scratch, I could not figure out how to rebase v3 into three clean
> commits if starting from v2).

Thanks, I've pushed these three patches to master now as
eb9a39c1b75a60fe3946496bb2eee8f32dbf09cd.

Thanks again,

Chris

Attachment: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]