unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Greg Hogan <code@greghogan.com>
Cc: 51592@debbugs.gnu.org
Subject: [bug#51592] [PATCH 0/2] gnu: Add bloomberg-bde.
Date: Wed, 01 Dec 2021 16:50:22 +0100	[thread overview]
Message-ID: <871r2w2ukh.fsf@gnu.org> (raw)
In-Reply-To: <CA+3U0ZnW4-9NpJrS1znf3w8jeNSKzL7+Aveu-hmjMfURXJbPRA@mail.gmail.com> (Greg Hogan's message of "Wed, 3 Nov 2021 15:12:31 -0400")

Hi,

Greg Hogan <code@greghogan.com> skribis:

> From 9fc2c247d937d587c54b634ec6fcca2b77e22f37 Mon Sep 17 00:00:00 2001
> From: Greg Hogan <code@greghogan.com>
> Date: Wed, 3 Nov 2021 15:22:19 +0000
> Subject: [PATCH 2/2] gnu: Add bloomberg-bde.
>
> * gnu/packages/cpp.scm (bloomberg-bde): New variable.

[...]

> +      (name "bloomberg-bde")
> +      ; Recent releases are not tagged so commit must be used for checkout.
> +      (version "3.93.0.0")
> +      (source (origin
> +                (method git-fetch)
> +                (uri (git-reference
> +                      (url "https://github.com/bloomberg/bde")
> +                      (commit commit)))

There are several bundled code bases, including pcre2, which is already
packaged.

Could you look into unbundling at least pcre2, and ideally all of these?
You can remove ‘thirdparty/’ subdirectories from the snippet.

If some of them are too hard to unbundle, we can leave a FIXME and
address them later.

Nitpick: Please use two semicolons to introduce comments that are on a
line of their own.  :-)

Thanks in advance, and apologies for the delay!

Ludo’.




  reply	other threads:[~2021-12-01 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 19:12 [bug#51592] [PATCH 0/2] gnu: Add bloomberg-bde Greg Hogan
2021-12-01 15:50 ` Ludovic Courtès [this message]
2021-12-21  1:26   ` Greg Hogan
2022-02-04 21:23     ` Greg Hogan
2022-02-08 17:19       ` bug#51592: " 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=871r2w2ukh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=51592@debbugs.gnu.org \
    --cc=code@greghogan.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).