From: "Tomáš Čech" <sleep_walker@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28698@debbugs.gnu.org
Subject: [bug#28698] [PATCH] gnu: Enable support for libpurple in bitlbee.
Date: Thu, 5 Oct 2017 23:13:04 +0200 [thread overview]
Message-ID: <20171005211304.46ogtyl75xb3mril@penguin> (raw)
In-Reply-To: <87vajv556r.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 811 bytes --]
Hi Ludo,
On Wed, Oct 04, 2017 at 03:00:12PM +0000, Ludovic Courtès wrote:
>Hi Tomáš!
>
>Tomáš Čech <sleep_walker@gnu.org> skribis:
>
>> * gnu/packages/messaging.scm (bitlbee): Add pidgin input, add more configure
>> flags.
>
>I think it’s a good idea, but it’s taking a lot of extra space:
>
>--8<---------------cut here---------------start------------->8---
>$ guix size bitlbee |tail -1
>total: 176.5 MiB
>$ guix size bitlbee pidgin |tail -1
>total: 668.0 MiB
>--8<---------------cut here---------------end--------------->8---
>
>What about adding a “lib” output to Pidgin? BitlBee would depend on
>that rather than on the whole Pidgin.
I agree - that is the best approach to split GUI and libpurple library,
I'll play with that.
Thanks for your review!
Tomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-05 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-04 8:04 [bug#28698] [PATCH] gnu: Enable support for libpurple in bitlbee Tomáš Čech
2017-10-04 15:00 ` Ludovic Courtès
2017-10-05 21:13 ` Tomáš Čech [this message]
2017-12-12 21:26 ` Oleg Pykhalov
2017-12-13 9:47 ` Ludovic Courtès
2022-01-13 15:52 ` bug#28698: " zimoun
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=20171005211304.46ogtyl75xb3mril@penguin \
--to=sleep_walker@gnu.org \
--cc=28698@debbugs.gnu.org \
--cc=ludo@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.