From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Allow disabling the build of all of systemd, leaving just udev
Date: Wed, 06 Jun 2012 04:23:47 +0000 [thread overview]
Message-ID: <4FCEDB53.4070005@gmail.com> (raw)
In-Reply-To: <4FC9B938.6020608@kadzban.is-a-geek.net>
Bryan Kadzban wrote:
> William Hubbs wrote:
>> I spoke with Kay on irc, and he expressed doubts that it will be
>> committed.
>
> Not being terribly inclined to set up an IRC client, were there any
> issues with the patch itself? Or does he just not like the idea at all
> for some reason? (Er, Kay? Maybe I should ask you directly. :-) )
>
>> However, I did get another suggestion from one of the guys there.
>>
>> Automake supports includes, so it would be good to break up
>> Makefile.am into several modules. That way it would be easy to
>> include them based on condissionals.
>>
>> I have started breaking things apart, but if you want, I can send you
>> the patch as I have it so far and we can collaborate on it. :-)
I'm interested in this too. However, I'm not sure what you are
referring to when you mention modules. Do you mean the automake
instruction 'include'?
The problem with udev as it's currently embedded in systemd is that the
udev programs require several systemd .c utility programs, although they
all build without the problematic libraries required by systemd
(intltool, d-bus, etc). These object files could be combined into each
of the udev programs without problems, but I'm having a problem
understanding the concept of what is acceptable.
AFAICT, there still needs to be a change to configure.ac to optionally
avoid all the extras that systemd needs. That seems to be where to
start, but we need support from upstream to get these changes into the
main distribution.
-- Bruce
next prev parent reply other threads:[~2012-06-06 4:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 6:56 [PATCH] Allow disabling the build of all of systemd, leaving just udev Bryan Kadzban
2012-06-02 20:49 ` William Hubbs
2012-06-03 16:55 ` Bryan Kadzban
2012-06-03 21:21 ` Bryan Kadzban
2012-06-03 21:22 ` William Hubbs
2012-06-03 22:00 ` Bryan Kadzban
2012-06-04 1:50 ` William Hubbs
2012-06-04 2:13 ` Bryan Kadzban
2012-06-04 18:51 ` William Hubbs
2012-06-05 3:10 ` Bryan Kadzban
2012-06-05 17:56 ` William Hubbs
2012-06-06 3:45 ` Bryan Kadzban
2012-06-06 4:23 ` Bruce Dubbs [this message]
2012-06-06 12:38 ` Dan Nicholson
2012-06-06 16:52 ` William Hubbs
2012-06-06 17:15 ` William Hubbs
2012-06-06 18:51 ` Bruce Dubbs
2012-06-06 22:53 ` William Hubbs
2012-06-07 13:34 ` Dan Nicholson
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=4FCEDB53.4070005@gmail.com \
--to=bruce.dubbs@gmail.com \
--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).