From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] 1.0.0-rc17: Further fine-tuning for the build system?
Date: Sun, 7 Apr 2013 14:11:29 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1304071410400.1951@hadrien> (raw)
In-Reply-To: <5161618D.7050505@users.sourceforge.net>
On Sun, 7 Apr 2013, SF Markus Elfring wrote:
> >> Are you the project leader for this software?
> >
> > Yes, but build systems are very tricky and entirely out of my expertise.
>
> I can eventually help to become used to the usual software development in this
> application area.
>
>
> > As long as the system builds in some way, I don't see the need for
> > supporting every possible exotic combination.
>
> I hope that mistakes will be fixed in the near future.
>
>
> > Notably, building the software from some directory other than the one
> > in which the software is located seems completely unnecessary, as far
> > as I can see.
>
> If you want to improve the Autotools setup, you will get this feature easily.
> The usefulness of "out-of-source builds / parallel build trees" might become
> obvious if more configuration variants will be considered for the software
> generation.
>
>
> > I don't want to make changes that are inessential and that I don't understand.
>
> Would you like adjust Automake details?
>
> How do you think about to start corrections with the selection of corresponding
> make file names?
>
>
> > Any thing that one person proposes would have to be reviewed by someone else.
>
> Would Rene perform such review tasks eventually since he was involved as a
> Github committer?
I don't think so. The required expertises are quite different.
julia
next prev parent reply other threads:[~2013-04-07 12:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 21:02 [Cocci] 1.0.0-rc16: Further fine-tuning for the build system? SF Markus Elfring
2013-03-02 21:18 ` Julia Lawall
2013-03-04 11:35 ` SF Markus Elfring
2013-03-04 12:36 ` Julia Lawall
2013-03-04 12:37 ` Julia Lawall
2013-03-04 12:43 ` SF Markus Elfring
2013-03-04 12:48 ` Julia Lawall
2013-03-04 13:14 ` SF Markus Elfring
2013-03-04 13:54 ` SF Markus Elfring
2013-03-04 15:40 ` SF Markus Elfring
2013-03-04 15:47 ` Julia Lawall
2013-03-04 16:05 ` SF Markus Elfring
2013-03-05 8:36 ` Arie Middelkoop
2013-03-07 15:54 ` SF Markus Elfring
2013-03-07 16:27 ` Arie Middelkoop
2013-03-07 17:07 ` SF Markus Elfring
2013-03-16 20:07 ` SF Markus Elfring
2013-03-17 12:18 ` Arie Middelkoop
2013-03-18 9:50 ` SF Markus Elfring
2013-04-07 10:51 ` [Cocci] 1.0.0-rc17: " SF Markus Elfring
2013-04-07 11:05 ` Julia Lawall
2013-04-07 11:14 ` SF Markus Elfring
2013-04-07 11:20 ` Julia Lawall
2013-04-07 11:30 ` SF Markus Elfring
2013-04-07 11:43 ` Julia Lawall
2013-04-07 12:07 ` SF Markus Elfring
2013-04-07 12:11 ` Julia Lawall [this message]
2013-04-07 12:13 ` SF Markus Elfring
2013-04-26 8:14 ` [Cocci] 1.0.0-rc16: " Richard W.M. Jones
2013-04-26 9:10 ` SF Markus Elfring
2013-04-26 9:16 ` Richard W.M. Jones
2013-04-26 9:36 ` SF Markus Elfring
2013-04-26 9:52 ` Richard W.M. Jones
2013-04-26 10:15 ` SF Markus Elfring
2013-04-26 10:25 ` Julia Lawall
2013-04-26 11:03 ` Peter Senna Tschudin
2013-04-26 11:28 ` SF Markus Elfring
2013-04-29 9:52 ` [Cocci] 1.0.0-rc17: " SF 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=alpine.DEB.2.02.1304071410400.1951@hadrien \
--to=julia.lawall@lip6.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox