From: Rodrigo Morales <moralesrodrigo1100@gmail.com>
To: help-guix@gnu.org
Subject: Most used and least used build-system in Guix packages
Date: Wed, 12 Apr 2023 23:04:44 +0000 [thread overview]
Message-ID: <CAGxMbPZ7OFMfhmrwtJxymZJHsqu0DamRC=innQd99XOaSuQwBA@mail.gmail.com> (raw)
Table of Contents
_________________
1. TL; DR
2. My findings
3. The question
1 TL; DR
========
Today, I was wondering what the most used build system and the least
one are. The most used build system is `gnu-build-system'. The least
used build system is `dub-build-system'. Here's how I found that out.
2 My findings
=============
,----
| (car %load-path)
`----
,----
|
/gnu/store/zc7dzsd10dd3pw60hircphz4vh1wlki0-guix-module-union/share/guile/site/3.0
`----
,----
|
dir="/gnu/store/zc7dzsd10dd3pw60hircphz4vh1wlki0-guix-module-union/share/guile/site/3.0"
| path="$dir/gnu/packages"
| grep -hREo '[a-zo-]+-build-system' $path | sort | uniq -c | sort -nr
`----
,----
| 3893 gnu-build-system
| 2717 python-build-system
| 2359 r-build-system
| 2188 cargo-build-system
| 1328 emacs-build-system
| 1176 cmake-build-system
| 841 perl-build-system
| 783 asdf-build-system
| 776 haskell-build-system
| 568 ruby-build-system
| 536 go-build-system
| 488 meson-build-system
| 361 ant-build-system
| 313 qt-build-system
| 299 julia-build-system
| 198 glib-or-gtk-build-system
| 198 dune-build-system
| 192 trivial-build-system
| 158 pyproject-build-system
| 154 copy-build-system
| 81 font-build-system
| 78 guile-build-system
| 75 texlive-build-system
| 52 ocaml-build-system
| 49 node-build-system
| 29 elm-build-system
| 21 rebar-build-system
| 21 rakudo-build-system
| 21 minetest-mod-build-system
| 20 waf-build-system
| 19 linux-module-build-system
| 15 minify-build-system
| 14 clojure-build-system
| 13 scons-build-system
| 12 android-ndk-build-system
| 9 patch-build-system
| 9 chicken-build-system
| 3 fix-build-system
| 3 channel-build-system
| 2 maven-build-system
| 1 tree-sitter-build-system
| 1 renpy-build-system
| 1 package-build-system
| 1 dub-build-system
`----
3 The question
==============
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...)
`----
next reply other threads:[~2023-04-12 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 23:04 Rodrigo Morales [this message]
2023-04-13 1:55 ` Most used and least used build-system in Guix packages Maxim Cournoyer
2023-04-13 9:40 ` Simon Tournier
2023-04-13 17:12 ` Martin Castillo
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='CAGxMbPZ7OFMfhmrwtJxymZJHsqu0DamRC=innQd99XOaSuQwBA@mail.gmail.com' \
--to=moralesrodrigo1100@gmail.com \
--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).