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] Request 339055 commented by jengelh (submit devel:tools/coccinelle)
Date: Thu, 22 Oct 2015 07:23:36 +0200	[thread overview]
Message-ID: <562872D8.3060004@users.sourceforge.net> (raw)
In-Reply-To: <alpine.LSU.2.20.1510150045200.18488@nerf40.vanv.qr>

> Since coccinelle.spec does not invoke autoreconf

How does the script "https://github.com/coccinelle/coccinelle/blob/a46bef70162d17cec6b0fc6101d737989f735ee4/autogen"
fit to your view?


> or any of the developer-side regenration tools,

Do you see any more software evolution there?


> we do not need autoconf/automake/libtool in the .spec at all.

Can it occasionally help to make more software dependencies explicit
also in the package specification?

Regards,
Markus

  reply	other threads:[~2015-10-22  5:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <obs-request-339055@build.opensuse.org>
     [not found] ` <561ec27032c86_2e7132ba18787fc@build.opensuse.org>
2015-10-14 21:04   ` [Cocci] Request 339055 commented by jengelh (submit devel:tools/coccinelle) Luis R. Rodriguez
2015-10-14 21:12     ` Jan Engelhardt
2015-10-14 21:23       ` Luis R. Rodriguez
2015-10-14 22:47         ` Jan Engelhardt
2015-10-22  5:23           ` SF Markus Elfring [this message]
2015-10-22  7:51             ` Jan Engelhardt
2015-10-22 10:32               ` SF Markus Elfring
2015-10-22 11:04                 ` Jan Engelhardt
2015-10-22 12:12                   ` SF Markus Elfring
2015-10-22 13:18               ` Luis R. Rodriguez
2015-12-10 15:17                 ` Sébastien Hinderer
2016-01-19 20:24                   ` Luis R. Rodriguez

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=562872D8.3060004@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.