From: "Ludovic Courtès" <ludo@gnu.org>
To: Meiyo Peng <meiyo.peng@gmail.com>
Cc: 33849-done@debbugs.gnu.org
Subject: bug#33849: [PATCH] gnu: Add polybar
Date: Tue, 25 Dec 2018 17:45:12 +0100 [thread overview]
Message-ID: <8736qlftd3.fsf@gnu.org> (raw)
In-Reply-To: <878t0f5tii.fsf@gmail.com> (Meiyo Peng's message of "Mon, 24 Dec 2018 14:27:33 +0800")
Hi,
Meiyo Peng <meiyo.peng@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>>> + (source
>>> + (origin
>>> + (method url-fetch)
>>> + (uri (string-append "https://github.com/jaagr/polybar/releases/"
>>> + "download/" version "/polybar.tar"))
>>> + (sha256
>>> + (base32 "1zpsvh1n77bx7s6mqqh3ba828k9xbp35c2mjmcl9nywfp6r5ldqi"))
>>> + (file-name (string-append name "-" version ".tar"))))
>>
>> Please use ‘git-fetch’ rather than downloading a generated tarball (it’s
>> a generated tarball, right?).
>
> No. This is a user uploaded release tarball. You can notice their
> difference. User uploaded tarball has "/releases/download/" in its URL.
>
> #+BEGIN_EXAMPLE
> User uploaded: https://github.com/jaagr/polybar/releases/download/3.3.0/polybar.tar
> Auto generated: https://github.com/jaagr/polybar/archive/3.3.0.tar.gz
> #+END_EXAMPLE
Oh right, so that’s OK.
> I tried to use the git-fetch method first, but it failed to build
> because git-fetch doesn't fetch git submodules. Do we support
> recursively fetching git submodules?
Yes, just add (recursive? #t).
>>From 3faa9dcf77ca83972db6234a9af6b22325ee0311 Mon Sep 17 00:00:00 2001
> From: Meiyo Peng <meiyo.peng@gmail.com>
> Date: Sun, 23 Dec 2018 23:05:38 +0800
> Subject: [PATCH] gnu: Add polybar.
>
> * gnu/packages/wm.scm (polybar): New variable.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2018-12-25 16:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 15:38 [bug#33849] [PATCH] gnu: Add polybar Meiyo Peng
2018-12-23 17:41 ` Ludovic Courtès
2018-12-24 6:27 ` Meiyo Peng
2018-12-25 16:45 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736qlftd3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33849-done@debbugs.gnu.org \
--cc=meiyo.peng@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.