From: Mark H Weaver <mhw@netris.org>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Erroneous uses of regex in the invokation of FIND-FILES
Date: Thu, 22 Aug 2019 16:49:21 -0400 [thread overview]
Message-ID: <87mug1ylg3.fsf@netris.org> (raw)
In-Reply-To: <864l29iki4.fsf@gmail.com> (Alex Vong's message of "Thu, 22 Aug 2019 18:04:35 +0800")
Hi Alex,
Alex Vong <alexvong1995@gmail.com> writes:
> I find out that there are a lof of erroneous uses of regex in the
> invokation of FIND-FILES. The correct usage should be:
>
> (find-files "." "\\.c$")
>
> Instead people write:
>
> (find-files "." ".*\\.c")
>
> which match unwanted files.
>
> For examples, in the procedure CUSTOM-GCC, the correct regex should be:
>
> "(c\\+\\+|cpp|g\\+\\+|gcov|gcc|gcc-.*)$"
>
> instead of:
>
> ".*(c\\+\\+|cpp|g\\+\\+|gcov|gcc|gcc-.*)"
>
> Please correct me if I am wrong.
You're right. It would be good to fix these problems incrementally, as
long as the changes don't cause too many rebuilds.
Changes to core packages will need to wait for now, since 'core-updates'
is frozen, and 'core-updates-next' should also be considered frozen,
since it will become 'core-updates' as soon as Berlin has built it out a
bit more. (The only change in 'core-updates-next' relative to
'core-updates' is that the new bootstrap tarballs have been fixed to be
deterministic.)
For some of these fixes, it might be best to apply them to 'staging'.
> Right now, the erroneous use of regex in CUSTOM-GCC casues the 'bin/'
> directory of the output of gccgo, gcc-objc and gcc-objc++ to be empty.
I'm uncertain how many rebuilds it would trigger to change 'custom-gcc',
and I don't have confidence that "guix refresh -l" is capable of giving
us a reliable answer. In the meantime, would you like to file a bug
report for this, so it's not forgotten?
Thanks for looking into it.
Best,
Mark
next prev parent reply other threads:[~2019-08-22 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 10:04 Erroneous uses of regex in the invokation of FIND-FILES Alex Vong
2019-08-22 20:49 ` Mark H Weaver [this message]
2019-09-20 20:31 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2019-08-22 10:14 Alex Vong
2019-09-20 19:52 ` Maxim Cournoyer
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=87mug1ylg3.fsf@netris.org \
--to=mhw@netris.org \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
/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).