linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Schwarzott <zzam@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-126 puts devices in /usr/local/dev
Date: Thu, 28 Aug 2008 09:12:38 +0000	[thread overview]
Message-ID: <200808281112.38749.zzam@gentoo.org> (raw)
In-Reply-To: <48B5F216.1000708@magtech.com.au>

On Donnerstag, 28. August 2008, Kay Sievers wrote:
> On Thu, Aug 28, 2008 at 06:50, Matthias Schwarzott <zzam@gentoo.org> wrote:
> > On Donnerstag, 28. August 2008, Marco d'Itri wrote:
> >> On Aug 28, David Zeuthen <david@fubar.dk> wrote:
> >> > If you don't pass any special options (such as prefix=/), the behavior
> >> > of putting device nodes in /usr/local/dev is indeed correct (it's
> >> > useful for e.g. debugging udev without screwing up the real /dev).
> >>
> >> This really looks like an excuse for an autoconfiscation bug.
> >> I have been maintaining an udev package for over four years and I never
> >> dreamt of rebuilding it with a different value of udev_root just for
> >> testing.
> >> It's much easier to set $UDEV_ROOT when debugging instead of forcing
> >> every package maintainer to set $prefix.
> >
> > The gentoo package now calls configure with these params:
> > --prefix=/ --includedir=/usr/include
>
> Huh? Why? Let prefix stay as usr, as usual, and set exec-prefix, as
> suggested in INSTALL. Just take a look at autogen.sh.
>

Ah, that simplifies it.
Thanks

Matthias

      parent reply	other threads:[~2008-08-28  9:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  0:32 udev-126 puts devices in /usr/local/dev Aras Vaichas
2008-08-28  0:39 ` David Zeuthen
2008-08-28  0:51 ` Marco d'Itri
2008-08-28  0:55 ` Aras Vaichas
2008-08-28  4:50 ` Matthias Schwarzott
2008-08-28  6:32 ` Kay Sievers
2008-08-28  9:12 ` Matthias Schwarzott [this message]

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=200808281112.38749.zzam@gentoo.org \
    --to=zzam@gentoo.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).