From: Michael Olbrich <m.olbrich@pengutronix.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] split --disable-extras into multiple options
Date: Wed, 03 Mar 2010 15:07:55 +0000 [thread overview]
Message-ID: <20100303150754.GC32004@pengutronix.de> (raw)
In-Reply-To: <20100211111209.GD30615@pengutronix.de>
On Wed, Mar 03, 2010 at 06:23:53AM -0800, Dan Nicholson wrote:
> I'm not that familiar with the udev setup, but I'd like to caution
> against surrounding these whole sections in an AM_CONDITIONAL. The
> preferred thing to do is surround just the parts that result in
> commands being run. For instance, I can see that you've here put
> dist_extras_gudev_libgudev_1_0_la_SOURCES under ENABLE_GUDEV. This
> will eventually break "make dist" if there person doing the
> distributing isn't building GUdev.
So you are saying, that if the section is disabled, then the files will be
skipped during "make dist", right?
So how would we handle "udevrules"?
"udevrulesdir" is always set but not all files in "dist_udevrules_DATA" are
always installed.
Would something like this work:
# unconditional stuff:
dist_udevrules_DATA += \
some_file
...
dist_modem_modeswitch_DATA = \
extras/modem-modeswitch/61-option-modem-modeswitch.rules \
extras/modem-modeswitch/61-mobile-action.rules
if ENABLE_MODEM_MODESWITCH
udevrules_DATA += dist_modem_modeswitch_DATA
libexec_PROGRAMS += extras/modem-modeswitch/modem-modeswitch
endif # ENABLE_MODEM_MODESWITCH
...
Regards,
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 |
next prev parent reply other threads:[~2010-03-03 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 11:12 [PATCH] split --disable-extras into multiple options Michael Olbrich
2010-02-13 12:51 ` Martin Pitt
2010-02-13 17:44 ` Bryan Kadzban
2010-02-13 18:11 ` Marco d'Itri
2010-03-02 13:21 ` Martin Pitt
2010-03-03 6:15 ` Michael Olbrich
2010-03-03 8:01 ` Martin Pitt
2010-03-03 14:23 ` Dan Nicholson
2010-03-03 15:07 ` Michael Olbrich [this message]
2010-03-03 16:46 ` Dan Nicholson
2010-03-09 12:14 ` Daniel Mierswa
2010-03-09 12:45 ` Martin Pitt
2010-03-09 16:37 ` 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=20100303150754.GC32004@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=linux-hotplug@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).