From: ludo@gnu.org (Ludovic Courtès)
To: Oleg Pykhalov <go.wigust@gmail.com>
Cc: 28698@debbugs.gnu.org
Subject: [bug#28698] [PATCH] gnu: Enable support for libpurple in bitlbee.
Date: Wed, 13 Dec 2017 10:47:30 +0100 [thread overview]
Message-ID: <87mv2ngdsd.fsf@gnu.org> (raw)
In-Reply-To: <87efnzk58n.fsf@gmail.com> (Oleg Pykhalov's message of "Wed, 13 Dec 2017 00:26:16 +0300")
Hello,
Oleg Pykhalov <go.wigust@gmail.com> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> 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:
>>
>> $ guix size bitlbee |tail -1
>> total: 176.5 MiB
>> $ guix size bitlbee pidgin |tail -1
>> total: 668.0 MiB
>>
>> What about adding a “lib” output to Pidgin? BitlBee would depend on
>> that rather than on the whole Pidgin.
>
> I want a libpurple support in bitlbee, too. So, here is a libpurple
> output, but still there is a big size because of inputs, I guess. :-(
Heheh, thanks for looking into it!
> Is there a way to decrease this?
[...]
> +++ b/gnu/packages/messaging.scm
> @@ -338,6 +338,7 @@ authentication.")
> "1y5p2mq3bfw35b66jsafmbva0w5gg1k99y9z8fyp3jfksqv3agcc"))
> (patches (search-patches "pidgin-add-search-path.patch"))))
> (build-system glib-or-gtk-build-system)
> + (outputs '("out" "libpurple"))
It should be “lib” instead of “libpurple”. If you do that, perhaps the
‘install-libpurple’ phase is no longer needed because ‘gnu-build-system’
will take care of it.
As for the size, it seems that GTK+ & co. are pulled in. Is there a way
to avoid it? Perhaps this comes from the .pc file?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-12-13 9:48 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
2017-12-12 21:26 ` Oleg Pykhalov
2017-12-13 9:47 ` Ludovic Courtès [this message]
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
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=87mv2ngdsd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28698@debbugs.gnu.org \
--cc=go.wigust@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).