all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: 60250@debbugs.gnu.org
Subject: [bug#60250] [PATCH] gnu: Add bees.
Date: Sat, 24 Dec 2022 19:34:32 +0800	[thread overview]
Message-ID: <87cz89xcfr.wl-hako@ultrarare.space> (raw)
In-Reply-To: <e86d8a06-0418-ebe5-3b63-288bb6b8de9d@disroot.org>

On Fri, 23 Dec 2022 15:57:53 +0800,
Adam Faiz wrote:
> > As pkg-config is only used for systemd, and markdown for documentations that won't be installed,
> > I'd rather remove them from native-inputs, WDYT?
> I agree that it should be done, but it's a shame that there's no install_docs rule in the
> Makefile. That should be a feature request/patch.
>
> I already have a bees-remove-bundled-cityhash.patch and bees-add-cityhash-to-install.md.patch to
> send upstream. Should I email them to you?

As v2 has unbundled cityhash, there's no need to send the patches to me.

One thing to mention is that, according to Repology[1], cityhash is not widely packaged, as a
result, it might be better to implement the unbundle as an option.

[1]: <https://repology.org/project/cityhash/versions>




  reply	other threads:[~2022-12-24 11:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22  8:19 [bug#60250] [PATCH] gnu: Add bees Hilton Chain via Guix-patches via
2022-12-22 18:52 ` Adam Faiz via Guix-patches via
2022-12-23  6:25   ` Hilton Chain via Guix-patches via
2022-12-23  6:35     ` [bug#60250] [PATCH v2] " Hilton Chain via Guix-patches via
2023-01-17 15:02       ` bug#60250: [PATCH] " Ludovic Courtès
2022-12-23  7:57     ` [bug#60250] " Adam Faiz via Guix-patches via
2022-12-24 11:34       ` Hilton Chain via Guix-patches via [this message]
2022-12-24 16:31         ` Adam Faiz via Guix-patches via
2022-12-22 19:22 ` Adam Faiz via Guix-patches via

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=87cz89xcfr.wl-hako@ultrarare.space \
    --to=guix-patches@gnu.org \
    --cc=60250@debbugs.gnu.org \
    --cc=adam.faiz@disroot.org \
    --cc=hako@ultrarare.space \
    /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.