From: rennes <rennes@openmailbox.org>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 27002@debbugs.gnu.org
Subject: [bug#27002] [PATCH] gnu: Add lollypop.
Date: Sat, 17 Jun 2017 22:21:28 -0500 [thread overview]
Message-ID: <5zz/xxCsCi29mKP7pwPmTx@XZ3vf3/+xpquFU9NVlkKk> (raw)
In-Reply-To: <87efukf5qc.fsf@gnu.org> (from ludo@gnu.org on Fri Jun 16 07:59:39 2017)
Hello,
thank you for your comments.
I had not noticed that in my profile I have installed
'gst-plugins-base'. I try to add 'gst-plugins-base' to Inputs but it
does not work, I will continue to test.
On the other hand, under the 'bin' directory I only see one binary for
lollipop:
jin@home ~$ l
/gnu/store/0psmp896kkijsszczmvbs0b9h7wfprdb-lollypop-0.9.240/bin/
total 12
-r-xr-xr-x 2 root root 2743 Dec 31 1969 lollypop
-r-xr-xr-x 2 root root 1523 Dec 31 1969 lollypop-cli
-r-xr-xr-x 2 root root 1529 Dec 31 1969 rhythmbox2lollypop
On 06/16/2017 07:59:39 AM, Ludovic Courtès wrote:
> Thomas Danckaert <post@thomasdanckaert.be> skribis:
>
> > I also noticed that the executable gets wrapped twice: bin/lollypop
> > wraps bin/.lollypop-real, which wraps bin/..lollypop-real-real :-)
> Can
> > this be avoided, or is it a side-effect of using the python build
> system
> > and wrapping the result?
>
> The ‘wrap-program’ procedure in (guix build utils) arranges things so
> as
> to never create double wrappers, so it would be interesting to see how
> this happened!
next prev parent reply other threads:[~2017-06-18 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 4:18 bug#27002: [PATCH] gnu: Add lollypop rennes
2017-06-16 12:08 ` [bug#27002] " Thomas Danckaert
2017-06-16 12:59 ` Ludovic Courtès
2017-06-18 3:21 ` rennes [this message]
2017-06-19 8:52 ` Thomas Danckaert
2017-06-24 18:06 ` rennes
2017-06-26 8:39 ` Thomas Danckaert
2017-07-11 9:11 ` bug#27002: " Ludovic Courtès
2017-06-19 13:28 ` [bug#27002] " Thomas Danckaert
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=5zz/xxCsCi29mKP7pwPmTx@XZ3vf3/+xpquFU9NVlkKk \
--to=rennes@openmailbox.org \
--cc=27002@debbugs.gnu.org \
--cc=post@thomasdanckaert.be \
/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).