From: "Gábor Boskovits" <boskovits@gmail.com>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gnu: profanity: Modify build options.
Date: Fri, 25 Oct 2019 14:10:41 +0200 [thread overview]
Message-ID: <CAE4v=pizLRK37Z9HSd5-AZ5Z9TX5T_7pYk8KdrU6bn8pNxuKVw@mail.gmail.com> (raw)
In-Reply-To: <20191025095547.qywu6lgz46fh6hdn@rafflesia>
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
Tanguy Le Carrour <tanguy@bioneland.org> ezt írta (időpont: 2019. okt. 25.,
Pén 11:59):
> Hi Guix!
>
> Yesterday, I submitted a patch to update Profanity [1].
>
> [1]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=37903
>
> My motivation was not to get the latest version of the software, but to
> get the OMEMO encryption feature! This was only possible with versions >
> 0.6.
>
> The question is now to know if I can/should modify the package's build
> options and dependencies to enable OMEMO? I guess it make sense to have
> encryption available by default.
>
> Another thing I would like to do is to enable profanity's "desktop"
> features,
> namely tray icon and notifications. Would it make sense to activate it
> by default? Would it be better to create a `profanity-desktop` package
> that modify the dependencies and the options?!
>
Usually the default package comes with as much functionality as possible.
You could do a minimal package
>
> What do you think?
>
> --
> Tanguy
>
>
[-- Attachment #2: Type: text/html, Size: 1664 bytes --]
next prev parent reply other threads:[~2019-10-25 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 9:55 gnu: profanity: Modify build options Tanguy Le Carrour
2019-10-25 12:10 ` Gábor Boskovits [this message]
2019-10-25 12:43 ` Tanguy Le Carrour
2019-10-25 14:51 ` Jack Hill
2019-10-25 15:09 ` Tanguy Le Carrour
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='CAE4v=pizLRK37Z9HSd5-AZ5Z9TX5T_7pYk8KdrU6bn8pNxuKVw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.org \
/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).