public inbox for cocci@systeme.lip6.fr
 help / color / mirror / Atom feed
From: Olaf Hering <olaf@aepfle.de>
To: Jacob Keller <jacob.e.keller@intel.com>
Cc: Julia Lawall <julia.lawall@inria.fr>, <cocci@inria.fr>
Subject: Re: [cocci] the future of bundles in coccinelle.git
Date: Wed, 19 Mar 2025 13:48:16 +0100	[thread overview]
Message-ID: <20250319134816.3b7d026c.olaf@aepfle.de> (raw)
In-Reply-To: <27f57368-6a2d-4ea4-8a81-b8bee42e2d5d@intel.com>

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

Tue, 18 Mar 2025 14:52:42 -0700 Jacob Keller <jacob.e.keller@intel.com>:

> Why not go the other route and optionally use the bundles?

What is there actual purpose, what does (any) bundle actually fix?

As you said, every bundle becomes stale. The way it is implemented
means one can not even test them because the one from the environment
takes precedence.

If one wants coccinelle, use the package manager to install it.
In case it is unavailable there, get a copy of opam and install it.
In case one has to actually work on coccinelle.git for whatever reason,
there can not be any convenience, except 'opam install coccinelle'
which will install all required development packages.

In the context of Packman I had to deal with way too many packages
that bundle something which has to be provided by the system.
Every single one was and is a mess to work with. Today my first reaction
when I see any bundle is: purge that repo from disk and do something else.
Which is what I'm going to do now.


Olaf

[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2025-03-19 12:48 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 [this message]
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

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=20250319134816.3b7d026c.olaf@aepfle.de \
    --to=olaf@aepfle.de \
    --cc=cocci@inria.fr \
    --cc=jacob.e.keller@intel.com \
    --cc=julia.lawall@inria.fr \
    /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