All of lore.kernel.org
 help / color / mirror / Atom feed
From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Build configuration challenges around "Menhir"
Date: Wed, 18 May 2016 11:22:27 +0200	[thread overview]
Message-ID: <af6302d2-0bf2-0877-d852-19b215e4e1a3@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1605181103490.2887@hadrien>

>> Who will dare to tackle open issues there a bit more?
> 
> In a general sense, perhaps no one.

I tried several times to improve corresponding software development challenges.
I am curious when more ideas will be picked up also by other contributors.


> If you have a specific issue in mind that is causing problems in practice
> (not just offending your sense of how things should be done), then you can report it
> with detailed information about your build environment,

This happened already over the mailing list and the GitHub issue tracker.


> and we will look at it.

How are the chances that source code review will evolve more?


> Alternatively, you are welcome to propose the code for what you consider
> to be the perfect build system.

I hope that expertise evolution will make it possible to fix remaining open issues.
How do you think about try any fine-tuning for the bundling (or other source determination)
of the involved software libraries?

Regards,
Markus

      reply	other threads:[~2016-05-18  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17 17:20 [Cocci] compiling latest coccinelle on opensuse Luis R. Rodriguez
2016-05-17 20:52 ` Julia Lawall
2016-05-17 22:44   ` Luis R. Rodriguez
2016-05-18  5:12     ` Julia Lawall
2016-05-18  8:28       ` [Cocci] Build configuration challenges around "Menhir" SF Markus Elfring
2016-05-18  8:43         ` Julia Lawall
2016-05-18  8:48           ` SF Markus Elfring
2016-05-18  9:08             ` Julia Lawall
2016-05-18  9:22               ` SF 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=af6302d2-0bf2-0877-d852-19b215e4e1a3@users.sourceforge.net \
    --to=elfring@users.sourceforge.net \
    --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.