From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] libkmod: version bump 18 -> 20
Date: Sat, 21 Mar 2015 14:34:06 +0100 [thread overview]
Message-ID: <20150321133406.GJ20453@pengutronix.de> (raw)
In-Reply-To: <20150307092305.GJ10717@pengutronix.de>
On Sat, Mar 07, 2015 at 10:23:05AM +0100, Uwe Kleine-König wrote:
> On Fri, Mar 06, 2015 at 08:54:41PM +0100, Robert Schwebel wrote:
> > On Fri, Mar 06, 2015 at 08:39:14PM +0100, Uwe Kleine-König wrote:
> > > On Fri, Mar 06, 2015 at 07:48:10PM +0100, Robert Schwebel wrote:
> > > > @@ -45,7 +45,8 @@ LIBKMOD_CONF_OPT := \
> > > > --disable-gtk-doc-html \
> > > > --disable-gtk-doc-pdf \
> > > > --without-xz \
> > > > - --$(call ptx/wwo, PTXCONF_LIBKMOD_ZLIB)-zlib
> > > > + --$(call ptx/wwo, PTXCONF_LIBKMOD_ZLIB)-zlib \
> > > > + --disable-coverage
> > > If you add a \ to the coverage line it doesn't need to be touched next
> > > time a new option is added.
> >
> > I don't think we do this for other packages.
> And this is an excuse not to do it now either? If you agree that it's a
> good idea, not having done that before shouldn't stop you.
>
> After all we never did libkmod 20 before :-)
And we rarely need it. The correct hunk looks like this:
@@ -41,6 +41,7 @@ LIBKMOD_CONF_OPT := \
--$(call ptx/endis, PTXCONF_LIBKMOD_LOGGING)-logging \
--$(call ptx/endis, PTXCONF_LIBKMOD_DEBUG)-debug \
--disable-python \
+ --disable-coverage \
--disable-gtk-doc \
--disable-gtk-doc-html \
--disable-gtk-doc-pdf \
Most options are added in the middle anyways.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-03-21 13:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 18:48 Robert Schwebel
2015-03-06 19:39 ` Uwe Kleine-König
2015-03-06 19:54 ` Robert Schwebel
2015-03-07 9:23 ` Uwe Kleine-König
2015-03-21 13:34 ` Michael Olbrich [this message]
2015-03-26 8:48 ` Michael Olbrich
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=20150321133406.GJ20453@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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