From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Allow disabling the build of all of systemd, leaving just udev
Date: Sun, 03 Jun 2012 21:22:09 +0000 [thread overview]
Message-ID: <20120603212209.GA19733@linux1> (raw)
In-Reply-To: <4FC9B938.6020608@kadzban.is-a-geek.net>
[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]
On Sun, Jun 03, 2012 at 09:55:55AM -0700, Bryan Kadzban wrote:
> William Hubbs wrote:
> > this looks good to me, but there are still pieces being installed
> > which should not be installed for a udev-only build afaik.
> >
> > You might want to look at removing those also.
>
> Which pieces?
>
> The only things that get installed in my case are the rules, udev.conf,
> systemd-udevd, udevadm, the helper binaries, the manpages, libudev, the
> udev and libudev pkg-config files, and stuff in /usr/share/doc. Though
> I do use a lot of the existing ./configure knobs to turn other systemd
> things off; maybe that's related.
Maybe it is, because I get the following things that would also be
installed:
etc/bash_completion.d
etc/systemd
usr/include/systemd
usr/lib/sysctl.d
usr/lib/systemd/system-generators
usr/lib/systemd/user
usr/share/man/man1
usr/share/man/man3
usr/share/man/man5
usr/share/polkit-1
usr/share/polkit-1/actions
usr/share/systemd
> Unless you mean the directories that are getting created, as in the
> previous message -- but I don't see a way to stop automake from doing
> that. Well, other than setting them to nothing in the Makefile.am if
> !ENABLE_SYSTEMD; duh, I should have done that. But that still seems a
> bit cosmetic to me.
Yes, I am referring to empty directories and I can see how you might
see it as cosmetic, but would you consider not creating the
directories?
> (One thing I need to do today is fix this so that "make distdir" works
> even with --disable-systemd. Should be able to pull the EXTRA_DIST
> stuff out of the conditionals to do that. So I'll probably look into
> setting these directories to nothing in that case as well.)
Ok, that may do it.
One more thing though, thinking about it, is that we will need the
systemd-tmpfiles tool because udev is not going to support the
/lib/udev/devices directory any longer for creating custom devices, so
you might want to still build and install all of the parts of that for a
standalone udev build if doing so doesn't bring in more dependencies.
Thanks,
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-06-03 21:22 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 [this message]
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
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=20120603212209.GA19733@linux1 \
--to=w.d.hubbs@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).