all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gnu: profanity: Modify build options.
Date: Fri, 25 Oct 2019 14:43:50 +0200	[thread overview]
Message-ID: <20191025124350.an35vgryo3wlv6p7@rafflesia> (raw)
In-Reply-To: <CAE4v=pizLRK37Z9HSd5-AZ5Z9TX5T_7pYk8KdrU6bn8pNxuKVw@mail.gmail.com>

Le 10/25, Gábor Boskovits a écrit :
> 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

OK, I'll work on that when Profanity 0.7 is available.

-- 
Tanguy

  reply	other threads:[~2019-10-25 12:43 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
2019-10-25 12:43   ` Tanguy Le Carrour [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191025124350.an35vgryo3wlv6p7@rafflesia \
    --to=tanguy@bioneland.org \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.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 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.