From: Logen Kain <walach.o...@gmail.com>
To: voidlinux@googlegroups.com
Subject: Profanity Notifications?
Date: Wed, 21 Jan 2015 18:04:41 -0800 (PST) [thread overview]
Message-ID: <4607da7d-2f3a-4a82-8739-4e8f7fe42d80@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1779 bytes --]
Someone brought to my attention that notifications don't seem to work with
Profanity so I decided to look at the pkg build:
# Template file for 'profanity'
2 pkgname=profanity
3 version=0.4.5
4 revision=1
5 # Package build options
6 build_options="notify xscreensaver"
7 build_style=gnu-configure
8 configure_args="$(vopt_enable notify notifications) $(vopt_with
xscreensaver)"
9 hostmakedepends="pkg-config"
10 makedepends="glib-devel expat-devel ncurses-devel libgcrypt-devel
libotr-devel
11 libcurl-devel libstrophe-devel $(vopt_if notifications libnotify-devel)
12 $(vopt_if xscreensaver libXScrnSaver-devel)"
13 short_desc="A console based XMPP client"
14 <email deleted due to being placed on google.
15 license="GPL-3"
16 homepage="http://www.profanity.im/"
17 distfiles="http://www.profanity.im/${pkgname}-${version}.tar.gz"
18
checksum=7436b38d03da0645f5cdb3ca3921b974a760ba68fa92e4def82519d759c7fc63
So I'm looking at the "vopt" commands and trying to wrap my head around it.
The best I can tell is that "vopt" makes it easier to select a build option
if I want to compile the package myself.
so... ./xbps-src -o "notify profanity" followed by "./xbps-src pkg
profanity" will build it with notify support correct?
Furthermore doing a "./xbps-src show-options foo" show both notify and
xscreensaver to be off. Looking at "$(vopt_enable notify notifications",
does this mean (pseudo code) "if enabled then notifications"? Reading from
the manual the enable should mean that build option "notify" is enabled by
default, or perhaps I misunderstand and, as I wrote above, it actually
means "if enabled then do this enable-<flag>"
If someone can clear this up in my head I'd appreciate it.
[-- Attachment #1.2: Type: text/html, Size: 3407 bytes --]
next reply other threads:[~2015-01-22 2:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 2:04 Logen Kain [this message]
2015-01-22 2:07 ` Logen Kain
2015-01-22 6:45 ` Juan RP
2015-01-22 20:58 ` Logen Kain
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=4607da7d-2f3a-4a82-8739-4e8f7fe42d80@googlegroups.com \
--to="walach.o..."@gmail.com \
--cc=voidlinux@googlegroups.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.
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 NNTP newsgroup(s).