From: William Hubbs <w.d.hubbs@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: sync udev rules directories with systemd units directories
Date: Sat, 14 Jul 2012 07:21:06 +0000 [thread overview]
Message-ID: <20120714072106.GA9323@linux1> (raw)
In-Reply-To: <1342214503-7931-1-git-send-email-w.d.hubbs@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
On Sat, Jul 14, 2012 at 07:52:23AM +0200, Marco d'Itri wrote:
> On Jul 14, William Hubbs <w.d.hubbs@gmail.com> wrote:
>
> > With the /usr merge coming, I'm thinking that packages that install
> > rules in /lib/udev/rules.d will have to be fixed to install them in
> > /usr/lib/udev/rules.d eventually, but until then, we should retain
> > support in udev to read from both places.
> >
> > Thoughts?
> Now I see the your point. I need to think a bit about the best
> solution for the transition period, but right now I suspect that it
> will be a /usr/lib/udev/rules.d/ to /lib/udev/rules.d/ symlink.
>
> (My problem is that I need to think when the symlink should be created
> and removed to support the merge, distributions which do not support
> upgrades do not need to care about this detail...)
I don't follow how a symlink either
/usr/lib/udev/rules.d->/lib/udev/rules.d or the other way around is
going to make the transition work smoothly for us. If we support both
locations as directories, once all of the packages that still install
things in /lib/udev/rules.d give us a way in their upstreams to install
the rules under /usr, /lib/udev/rules.d will just naturally disappear
from everyone's systems.
How is linking /usr/lib/udev/rules.d to /lib/udev/rules.d going to aid
in the transition? That seems to be going backward.
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-07-14 7:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 21:21 [PATCH] udev: sync udev rules directories with systemd units directories William Hubbs
2012-07-13 21:38 ` Kay Sievers
2012-07-13 22:48 ` William Hubbs
2012-07-13 23:06 ` Kay Sievers
2012-07-14 0:33 ` William Hubbs
2012-07-14 3:46 ` Marco d'Itri
2012-07-14 5:42 ` William Hubbs
2012-07-14 5:52 ` Marco d'Itri
2012-07-14 7:21 ` William Hubbs [this message]
2012-07-15 17:03 ` Martin Pitt
2012-07-15 17:14 ` Marco d'Itri
2012-07-15 17:45 ` Martin Pitt
2012-07-15 23:09 ` William Hubbs
2012-07-16 0:02 ` Kay Sievers
2012-07-16 0:06 ` Marco d'Itri
2012-07-16 0:26 ` Kay Sievers
2012-07-17 0:57 ` William Hubbs
2012-07-17 1:14 ` William Hubbs
2012-07-17 7:03 ` Lucas De Marchi
2012-07-17 11:46 ` Tom Gundersen
2012-07-17 23:44 ` William Hubbs
2012-07-17 23:50 ` Greg KH
2012-07-18 6:02 ` William Hubbs
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=20120714072106.GA9323@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).