From: ohering@suse.de (Olaf Hering)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Improvements for building the Coccinelle software
Date: Tue, 24 May 2016 22:08:28 +0200 [thread overview]
Message-ID: <20160524200828.GA7425@suse.de> (raw)
In-Reply-To: <1361a24e-9dc5-db4f-d347-370db8d126dc@users.sourceforge.net>
On Tue, May 24, SF Markus Elfring wrote:
>
> > There is now a pullrq to fix a bug in configure.ac,
>
> I am curious when the script "setup/cocci.m4" will be updated.
> https://github.com/coccinelle/coccinelle/pull/70
When a new release is cut the release manager runs autogen.sh. In an
ideal world everyone runs autogen.sh because keeping
automake/autoconf/.. uptodate is cheap. The world failed to do that.
Thats why each and every pkg includes a configure script. Some store
them even in the SCM.
> Would you like to improve the involved build scripts any more?
> https://github.com/coccinelle/coccinelle/issues/42
What improvements do you have in mind?
> > and also a new pkg named ocaml-parmap to replace the built-in copy.
>
> How much do you care for software bundling?
If certain software has dependencies its not the task of that software
to provide them. So, drop the bundled stuff.
Olaf
next prev parent reply other threads:[~2016-05-24 20:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 19:17 [Cocci] github update Julia Lawall
2016-05-23 16:37 ` Luis R. Rodriguez
2016-05-23 16:39 ` Julia Lawall
2016-05-23 20:31 ` Julia Lawall
2016-05-23 20:37 ` Luis R. Rodriguez
2016-05-23 20:49 ` Julia Lawall
2016-05-23 21:19 ` Luis R. Rodriguez
2016-05-23 21:25 ` Olaf Hering
2016-05-23 21:37 ` Julia Lawall
2016-05-23 21:37 ` Julia Lawall
2016-05-23 21:41 ` Luis R. Rodriguez
2016-05-23 21:44 ` Julia Lawall
2016-05-23 21:49 ` Luis R. Rodriguez
2016-05-24 13:32 ` Olaf Hering
2016-05-24 20:00 ` [Cocci] Improvements for building the Coccinelle software SF Markus Elfring
2016-05-24 20:08 ` Olaf Hering [this message]
2016-05-24 20:17 ` SF Markus Elfring
2016-05-24 20:59 ` Olaf Hering
2016-05-25 7:18 ` SF Markus Elfring
2016-05-25 7:45 ` Olaf Hering
2016-05-25 7:54 ` SF Markus Elfring
2016-05-25 8:02 ` Olaf Hering
2016-05-25 8:15 ` SF Markus Elfring
2016-05-24 20:23 ` Julia Lawall
2016-05-24 21:02 ` Olaf Hering
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=20160524200828.GA7425@suse.de \
--to=ohering@suse.de \
--cc=cocci@systeme.lip6.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 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.