unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: "Ludovic Courtès" <ludo@gnu.org>, "Tobias Geerinckx-Rice" <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: git / grep with pcre support?
Date: Wed, 30 Oct 2019 17:33:54 +0100	[thread overview]
Message-ID: <87k18m6vm5.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87y3148san.fsf@ambrevar.xyz>

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

I've sent patch 37994 for git.
If triggers the rebuilt of just under 300 packages, so I guess it's safe
for master?

For grep:
actually our `grep' package has pcre support.
It's grep-final which doesn't:

--8<---------------cut here---------------start------------->8---
(define grep-final
  ;; The final grep.  Gzip holds a reference to it (via zgrep), so it must be
  ;; built before gzip.
  (let ((grep (with-boot5 (package-with-bootstrap-guile grep))))
    (package/inherit grep
                     (inputs (alist-delete "pcre" (package-inputs grep)))
                     (native-inputs `(("perl" ,perl-boot0))))))
--8<---------------cut here---------------end--------------->8---

Is there a reason for removing pcre here?
It does not add more than 2 MiB to the closure size.  Maybe a graph
simplification issue?

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2019-10-30 16:34 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
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 [this message]
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=87k18m6vm5.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    /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).