From: Markus Elfring <Markus.Elfring@web.de>
To: Olaf Hering <olaf@aepfle.de>, cocci@inria.fr
Subject: Re: [cocci] the future of bundles in coccinelle.git
Date: Tue, 18 Mar 2025 16:18:03 +0100 [thread overview]
Message-ID: <d508db9c-fa5a-4aac-b4ee-d67573d5aaa5@web.de> (raw)
In-Reply-To: <20250318111305.281abcca.olaf@aepfle.de>
> While looking for the proper way to import pcre2, I realized that the
> way configure.ac looks for required OCaml libraries is ... weird.
I find such a view interesting somehow.
> There is no way to force the usage of the variants in bundles/,
> the version provided by ocamlfind is always preferred.
There are remaining system configuration challenges to consider.
https://en.wikipedia.org/wiki/Product_bundling#Software
> I think since a while the required build environment is easy to create
> with either 'opam install $ALL_BUNDLES', or 'zypper install $packages'.
Corresponding software dependencies might trigger further concerns.
> Hence I suggest to remove bundles/ and all code referring to it.
I propose to take further case distinctions better into account
so that the involved software build system can become safer and more convenient.
Regards,
Markus
prev parent reply other threads:[~2025-03-18 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:13 [cocci] the future of bundles in coccinelle.git Olaf Hering
2025-03-18 10:19 ` Julia Lawall
2025-03-18 10:35 ` Olaf Hering
2025-03-18 21:52 ` Jacob Keller
2025-03-18 22:03 ` Julia Lawall
2025-03-19 12:48 ` Olaf Hering
2025-03-19 13:07 ` Markus Elfring
2025-03-19 13:20 ` Julia Lawall
2025-03-19 13:11 ` Victor Gambier
2025-03-19 13:18 ` Julia Lawall
2025-03-19 13:31 ` Victor Gambier
2025-03-19 13:33 ` Julia Lawall
2025-03-19 13:47 ` Victor Gambier
2025-03-19 13:21 ` Julia Lawall
2025-03-18 15:18 ` Markus Elfring [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d508db9c-fa5a-4aac-b4ee-d67573d5aaa5@web.de \
--to=markus.elfring@web.de \
--cc=cocci@inria.fr \
--cc=olaf@aepfle.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.