unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Gabriel Arazas <foo.dogsquared@gmail.com>
To: 43378@debbugs.gnu.org
Subject: [bug#43378] [PATCH] Update rofi to 1.6.0.
Date: Sun, 13 Sep 2020 21:54:32 +0800	[thread overview]
Message-ID: <1df486c8-3ce8-b196-912f-0b728ac06dd9@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 465 bytes --]

I don't know if this is currently being updated by someone else. I've 
searched the Debbugs issue tracker for this before completing this but 
better be done than nothing, I guess.

There is an attached patch that updates rofi to 1.6.0 as released at 
least a week ago ( https://github.com/davatorium/rofi/releases/tag/1.6.0 ).

I've tested the build with the latest features (e.g., custom mode 
scripts, initial media support) and it is working so far on my end.


[-- Attachment #2: 0001-gnu-rofi-Update-to-1.6.0.patch --]
[-- Type: text/x-patch, Size: 1832 bytes --]

From 9199caf17c4112fb6e1c8a12977052cfb2265f83 Mon Sep 17 00:00:00 2001
From: Gabriel Arazas <foo.dogsquared@gmail.com>
Date: Sun, 13 Sep 2020 21:39:12 +0800
Subject: [PATCH] gnu: rofi: Update to 1.6.0.

* gnu/packages/xdisorg.scm (rofi): Update to 1.6.0.
[inputs]: Add libjpeg-turbo.
---
 gnu/packages/xdisorg.scm | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm
index 50cde39e81..44f903ccb0 100644
--- a/gnu/packages/xdisorg.scm
+++ b/gnu/packages/xdisorg.scm
@@ -39,6 +39,7 @@
 ;;; Copyright © 2020 Alex McGrath <amk@amk.ie>
 ;;; Copyright © 2020 Ivan Kozlov <kanichos@yandex.ru>
 ;;; Copyright © 2020 Brett Gilio <brettg@gnu.org>
+;;; Copyright © 2020 Gabriel Arazas <foo.dogsquared@gmail.com>
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -1453,7 +1454,7 @@ connectivity of the X server running on a particular @code{DISPLAY}.")
 (define-public rofi
   (package
     (name "rofi")
-    (version "1.5.4")
+    (version "1.6.0")
     (source (origin
               (method url-fetch)
               (uri (string-append "https://github.com/DaveDavenport/rofi/"
@@ -1461,13 +1462,14 @@ connectivity of the X server running on a particular @code{DISPLAY}.")
                                   version "/rofi-" version ".tar.xz"))
               (sha256
                (base32
-                "1nslmyqyzhfr4hxd4llqkkkb8ap8apkdna32rllvar7r576059ci"))))
+                "0566b499lbpfb1gk4p17iw78ywmk9l2jww1kqjbdanrl22hai1y4"))))
     (build-system gnu-build-system)
     (inputs
      `(("pango" ,pango)
        ("cairo" ,cairo)
        ("glib" ,glib)
        ("startup-notification" ,startup-notification)
+       ("libjpeg" ,libjpeg-turbo)
        ("librsvg" ,librsvg)
        ("libxkbcommon" ,libxkbcommon)
        ("libxcb" ,libxcb)
-- 
2.28.0


             reply	other threads:[~2020-09-13 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-13 13:54 Gabriel Arazas [this message]
2020-09-14  7:12 ` bug#43378: [PATCH] Update rofi to 1.6.0 Efraim Flashner

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=1df486c8-3ce8-b196-912f-0b728ac06dd9@gmail.com \
    --to=foo.dogsquared@gmail.com \
    --cc=43378@debbugs.gnu.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).