all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alex Vong <alexvong1995@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/3] gnu: vlc: Add inputs.
Date: Mon, 10 Oct 2016 23:37:03 +0800	[thread overview]
Message-ID: <87int0p65c.fsf@gmail.com> (raw)
In-Reply-To: <87lgxwfe39.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 10 Oct 2016 16:55:38 +0200")

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

Hello,

Ricardo Wurmus <rekado@elephly.net> writes:

> Alex Vong <alexvong1995@gmail.com> writes:
>
>
>> * gnu/packages/video.scm (vlc)[inputs]: Add eudev, faad2, fluidsynth,
>>   gnome-vfs, gst-plugins-base, gtk+-2, jack-2, libass, libavc1394,
>>   libbluray, libcaca, libdca, libdvdnav, libdvdread, libmpeg2,
>>   libmodplug, libmtp, libnotify, libraw1394, libshout, librsvg, libupnp,
>>   libva, libvdpau, samba, taglib, twolame.
>
> Please use “jack-1” instead of “jack-2”.  They both work but we use
> “jack-1” everywhere.
>
> “jack-2” offers DBUS activation — if a user wants to have this they can
> install “jack-2” into their profile and it will work just fine with
> applications that were linked with “jack-1”.
>
> In short: “jack-2” is only there for users who want DBUS support in
> their JACK server, “jack-1” is for everyone and everything else.
>
> ~~ Ricardo

I think the new patch I send today uses jack-1 instead of jack-2. I must
have forgotten to mention I make the switch.

Cheers,
Alex

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 454 bytes --]

      reply	other threads:[~2016-10-10 15:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-10  3:08 [PATCH 3/3] gnu: vlc: Add inputs Alex Vong
2016-09-20 20:09 ` Leo Famulari
2016-10-10 10:38   ` Alex Vong
2016-10-10 14:55 ` Ricardo Wurmus
2016-10-10 15:37   ` Alex Vong [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=87int0p65c.fsf@gmail.com \
    --to=alexvong1995@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.