From: Guillaume Le Vaillant <glv@posteo.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: 41689@debbugs.gnu.org
Subject: [bug#41689] Add cl-rdkafka
Date: Sun, 07 Jun 2020 11:17:40 +0200 [thread overview]
Message-ID: <878sgzb5fv.fsf@yamatai> (raw)
In-Reply-To: <CA+TvSRibuVJ2c3wQftqoAvwQO54huaN8unM=p3Z5FgYyrLFV-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Katherine Cox-Buday <cox.katherine.e@gmail.com> skribis:
> That is a mistake; there's no reason it can't be listed as a regular input.
>
> During my tests to confirm this, I realized that sbcl-cl-rdkafka
> wasn't actually producing any useful output. This led me down a
> rabbit-hole (albeit a productive one). Below is a new patch set.
>
> 11:23 kate says: guix refresh -l sbcl-lparallel
> Building the following 4 packages would ensure 8 dependent packages
> are rebuilt: ecl-cl-rdkafka@1.0.2 cl-rdkafka@1.0.2
> cl-random-forest@0.1-0.85fbdd4 next@1.5.0
>
> All dependent packages continue to build.
>
> On Fri, Jun 5, 2020 at 9:01 AM Guillaume Le Vaillant <glv@posteo.net> wrote:
>>
>>
>> Hi,
>>
>> Katherine Cox-Buday <cox.katherine.e@gmail.com> skribis:
>>
>> > (propagated-inputs
>> > `(("librdkafka" ,librdkafka)))
>>
>> Why is the librdkafka library a propagated input instead of a regular
>> input?
Thanks. Patches pushed as 388a89750ec60a320dd7b6a0b0f174cbed4f50c6 and
64174aff927f4f9da18ea452247c838e6bab3306. Except I didn't push the
definition for ecl-cl-rdkafka because it didn't build (because of the
phase moving a file before the cleanup phase IIRC).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-06-07 9:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 14:36 [bug#41689] Add cl-rdkafka Katherine Cox-Buday
2020-06-05 14:01 ` Guillaume Le Vaillant
2020-06-06 16:24 ` Katherine Cox-Buday
2020-06-07 9:17 ` Guillaume Le Vaillant [this message]
2020-06-23 21:50 ` Ludovic Courtès
2020-06-23 22:26 ` Katherine Cox-Buday
2020-06-24 13:11 ` bug#41689: " Ludovic Courtès
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=878sgzb5fv.fsf@yamatai \
--to=glv@posteo.net \
--cc=41689@debbugs.gnu.org \
--cc=cox.katherine.e@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).