linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: systemd-183
Date: Thu, 31 May 2012 17:35:49 +0000	[thread overview]
Message-ID: <20120531173549.GB1373@linux1> (raw)
In-Reply-To: <4FBE8DC4.1070202@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

Hi Kay,

On Sun, May 27, 2012 at 01:34:11PM +0200, Kay Sievers wrote:
> We support stand-alone *operation* of the udev tools, but the build
> system does not support a stand-alone *build*. The systemd tree needs
> to be built and udev picked out of it.
> 
> There are also several other generally useful tools in the built tree,
> which you might need too over time, like tmpfiles, module-load,
> sysconf, binfmt,  ... A couple of D-Bus services to manage system
> settings from the desktop.
> 
> Various upstream tools start to install config files or use these
> interfaces. It might be the simplest to install them too, even when
> systemd is not used.

I understand that folks might want these tools, but I don't want to
install the ones that udev doesn't need as part of the udev package. I
am also concerned about libcap and dbus being hard requirements of the
udev build process.

If udev, or the tools that it needs, like tmpfiles, requires these
libraries, that is one thing, otherwise I really do not want
to make them dependencies of the udev package. The issue is that in
gentoo, since we are source based, I would have to require all of our
users to install dbus and libcap just to build udev.

Do you have any suggestions?

Thanks,

William


[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-05-31 17:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-24 19:36 systemd-183 Bruce Dubbs
2012-05-27  0:54 ` systemd-183 William Hubbs
2012-05-27  3:19 ` systemd-183 Karl O. Pinc
2012-05-27  3:38 ` systemd-183 Bruce Dubbs
2012-05-27  4:06 ` systemd-183 Karl O. Pinc
2012-05-27 11:34 ` systemd-183 Kay Sievers
2012-05-27 12:17 ` systemd-183 Karl O. Pinc
2012-05-31 17:35 ` William Hubbs [this message]
2012-05-31 19:33 ` systemd-183 Bruce Dubbs
2012-05-31 19:46 ` systemd-183 Tom Gundersen
2012-05-31 19:57 ` systemd-183 Kay Sievers
2012-05-31 20:15 ` systemd-183 Kay Sievers
2012-05-31 20:30 ` systemd-183 Bruce Dubbs
2012-05-31 20:52 ` systemd-183 Kay Sievers
2012-05-31 21:45 ` systemd-183 Tom Gundersen

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=20120531173549.GB1373@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).