From: Arun Isaac <arunisaac@systemreboot.net>
To: Alex Vong <alexvong1995@gmail.com>
Cc: 27643@debbugs.gnu.org
Subject: [bug#27643] [PATCH] gnu: Add simplescreenrecorder.
Date: Tue, 11 Jul 2017 19:47:02 +0530 [thread overview]
Message-ID: <4de25aef.AEEANLs8YQIAAAAAAAAAAAPSojkAAAACwQwAAAAAAAW9WABZZN3o@mailjet.com> (raw)
In-Reply-To: <87y3rvcd29.fsf@gmail.com>
>>> + ("qt" ,qt-4) ; README.md: using Qt 5 causes some stability issues
>>> + ("ffmpeg" ,ffmpeg)
>>> + ("alsa-lib" ,alsa-lib)
>>> + ("pulseaudio" ,pulseaudio)
>>> + ("jack" ,jack-1)
>>> + ("glu" ,glu)
>>> + ("libx11" ,libx11)
>>> + ("libxfixes" ,libxfixes)
>>> + ("libxext" ,libxext)
>>
>> The package builds successfully without libx11, libxfixes and libxext
>> included as inputs. Are you sure they are needed? Could you check again?
>>
>>> + ("libxi" ,libxi)))
>>
> These packages are listed as Build dependencies in README[0]. What do
> you think?
I think we should not include them as dependencies. We can always
include them later if we have problems.
I did start the application built without these packages, and it started
successfully. If you are a user of this package, you could test it more
extensively.
WDYT?
next prev parent reply other threads:[~2017-07-11 14:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 16:16 [bug#27643] [PATCH] gnu: Add simplescreenrecorder Alex Vong
2017-07-10 20:15 ` Arun Isaac
[not found] ` <a885d32b.ADkAACOBA2kAAAAAAAAAAAPSfd8AAAACwQwAAAAAAAW9WABZY-Bh@mailjet.com>
2017-07-11 13:34 ` Alex Vong
2017-07-11 13:45 ` Alex Vong
2017-07-11 14:17 ` Arun Isaac [this message]
[not found] ` <9a059d85.AEEANLs8YQMAAAAAAAAAAAPSfd8AAAACwQwAAAAAAAW9WABZZN3o@mailjet.com>
2017-07-11 15:22 ` Alex Vong
2017-07-11 17:41 ` Arun Isaac
2017-07-12 20:32 ` bug#27643: " Arun Isaac
[not found] ` <4ebf0597.AEUAMuQMiowAAAAAAAAAAAPSfd8AAAACwQwAAAAAAAW9WABZZod0@mailjet.com>
2017-07-13 13:59 ` [bug#27643] " Alex Vong
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=4de25aef.AEEANLs8YQIAAAAAAAAAAAPSojkAAAACwQwAAAAAAAW9WABZZN3o@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=27643@debbugs.gnu.org \
--cc=alexvong1995@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 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).