From: Martin Castillo <castilma@uni-bremen.de>
To: help-guix@gnu.org
Subject: Re: Most used and least used build-system in Guix packages
Date: Thu, 13 Apr 2023 19:12:41 +0200 [thread overview]
Message-ID: <df1a451a-8506-e1d4-1793-2cf765cbb9ff@uni-bremen.de> (raw)
In-Reply-To: <CAGxMbPZ7OFMfhmrwtJxymZJHsqu0DamRC=innQd99XOaSuQwBA@mail.gmail.com>
> ==============
>
> Does anyone know if there's a more accurate way of finding out this
> information? I'm asking because my method also counts build systems
> that are mentioned in comments. For example, if a file contains
> comments that mention build systems, they are also counted.
>
> ,----
> | (... more sentences that mention dub-build-system...)
> | ;; One sentence that mentions dub-build-system
> | ;; Another sentence that mentions dub-build-system
> | (... more sentences that mention dub-build-system...)
> `----
maybe filter out comment lines ?
grep -hREo '^[^;]+[a-zo-]+-build-system' $path | sort | uniq -c | sort -nr
prev parent reply other threads:[~2023-04-13 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 23:04 Most used and least used build-system in Guix packages Rodrigo Morales
2023-04-13 1:55 ` Maxim Cournoyer
2023-04-13 9:40 ` Simon Tournier
2023-04-13 17:12 ` Martin Castillo [this message]
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=df1a451a-8506-e1d4-1793-2cf765cbb9ff@uni-bremen.de \
--to=castilma@uni-bremen.de \
--cc=help-guix@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.
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).