unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: git / grep with pcre support?
Date: Mon, 8 Jul 2019 09:48:07 +0300	[thread overview]
Message-ID: <20190708064807.GI1085@macbook41> (raw)
In-Reply-To: <878staujbv.fsf@ambrevar.xyz>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

On Sun, Jul 07, 2019 at 02:20:52PM +0200, Pierre Neidhardt wrote:
> Hi!
> 
> Quite a few packages depend on grep to have PCRE support (e.g. freebayes).
> 
> Similarly, some packages (magit-todos) depend on git to be built with
> PCRE support.
> Compiling Git with USE_LIBPCRE2 would fix this.
> 
> I understand that adding PCRE support to those packages might increase
> their closure size, which might not be desirable for such fundamental
> packages.
> 
> What about grep-minimal and git-minimal packages then?

We do actually already have a git-minimal, it's used for git-fetch
references :)

'guix size git' => 411 MiB
'guix size git pcre' => 413 MiB

'guix size grep' => 71.4 MiB
'guix size grep pcre' => 71.4 MiB

Looks like a good idea to me.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-07-08  6:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-07 12:20 git / grep with pcre support? Pierre Neidhardt
2019-07-08  6:48 ` Efraim Flashner [this message]
2019-07-08 15:42   ` Tobias Geerinckx-Rice
2019-07-11 15:55     ` Ludovic Courtès
2019-07-11 16:11       ` Pierre Neidhardt
2019-10-30 16:33         ` Pierre Neidhardt
2019-11-06 10:01           ` Pierre Neidhardt
2020-05-20  9:04             ` Pierre Neidhardt

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=20190708064807.GI1085@macbook41 \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).