From: Marcel Holtmann <marcel@holtmann.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Add rulesdir to libudev.pc
Date: Thu, 08 Jan 2009 22:47:31 +0000 [thread overview]
Message-ID: <1231454851.5298.32.camel@californication> (raw)
In-Reply-To: <1231444183.5298.24.camel@californication>
Hi Kay,
> > I think we should add a rulesdir entry like for example PolicKit does
> > for its policy files. Attached patch does this. Please check if this
> > makes sense to you.
>
> I don't mind, but the rules directory is only interesting for the
> daemon, not the library, you can even specify the location in the udev
> config file, or at daemon startup.
I know, but that is a total different story. For external applications
we need to know at least the default udev rules.d location. If then this
gets overwritten by a command line option, you can't do much about it
anyway.
> The problem is that we can not use prefix, which is /usr. If we use
> udev_prefix, which would be the right value, we get the non-expanded
> value in the pkgconfig file, but because we fake exec_prefix here, we
> are back to the inconsistency Inaky mentioned yesterday. :)
>
> Maybe we should drop that exec_prefix use und invent --slibdir (s like
> in --(s)bindir), which other projects think about to introduce, and we
> would require: --prefix, --libdir=, --slibdir=, --sbindir> --sysconf-dir to be specified at configure time? Maybe that's easier
> to handle, I was just waiting what the glib guys plan to use, because
> they have similar problems with configure specifying the rootfs as
> install location.
What about libexecdir since configure has already support for it. Just
base everything of on that one.
Regards
Marcel
next prev parent reply other threads:[~2009-01-08 22:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 19:49 Add rulesdir to libudev.pc Marcel Holtmann
2009-01-08 21:43 ` Kay Sievers
2009-01-08 22:47 ` Marcel Holtmann [this message]
2009-01-08 22:54 ` Kay Sievers
2009-01-15 22:59 ` Karel Zak
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=1231454851.5298.32.camel@californication \
--to=marcel@holtmann.org \
--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).