| 1 |
Philip Webb <purslow@××××××××.net> posted |
| 2 |
20090520061752.GA4750@××××××××.net, excerpted below, on Wed, 20 May 2009 |
| 3 |
02:17:52 -0400: |
| 4 |
|
| 5 |
> The dir belongs to Dbus |
| 6 |
> |
| 7 |
> root:509 xinitrc.d> equery belongs /etc/X11/xinit/xinitrc.d |
| 8 |
> [ Searching for file(s) /etc/X11/xinit/xinitrc.d in *... ] |
| 9 |
> sys-apps/dbus-1.2.3-r1 (/etc/X11/xinit/xinitrc.d) |
| 10 |
|
| 11 |
Yes, but note how dirs in general "belong" to packages. Unlike files and |
| 12 |
file collision, dirs don't collide, they're simply shared. |
| 13 |
|
| 14 |
Try equery b /usr/share/doc for instance... or in a more directly |
| 15 |
parallel to our current dir comparison, /etc/init.d . |
| 16 |
|
| 17 |
The idea is that when a package owning a dir is removed, if the dir is |
| 18 |
empty, it too is removed. That's also why certain system dirs have |
| 19 |
.keep-<pkg> files in them, so they won't be removed as empty dirs until |
| 20 |
that package is removed. |
| 21 |
|
| 22 |
This behavior is actually very handy in some cases, tho. It's easy to |
| 23 |
determine how many packages have contents in a particular directory |
| 24 |
without equerying every file therein. Especially for long lasting |
| 25 |
installations that have been continuously upgraded for years, with |
| 26 |
portage's behavior on owned and orphaned files changing a bit over the |
| 27 |
years, it's possible various obscure dirs will have content the user |
| 28 |
doesn't remember putting there and no package owns. I expect there'll be |
| 29 |
several files left over in /usr/kde/3.5 when I finally remove it, for |
| 30 |
instance, and being able to confirm for sure that no packages own the dir |
| 31 |
any more, or finding the stray KDE 3.5 packages I didn't remove and still |
| 32 |
need to, can be very useful before I actually manually delete the |
| 33 |
directory and any remaining content itself. This was certainly the case |
| 34 |
with /usr/kde/3.4 I know, as I remember cleaning it up. |
| 35 |
|
| 36 |
So, just because dbus owns the dir doesn't mean a thing, in terms of |
| 37 |
whether other packages can own and put stuff in it too. Note that I |
| 38 |
really don't know much bout /etc/X11/xinit/xinitrc.d and its purposes. |
| 39 |
I'm just saying that you can't use the fact that it currently just |
| 40 |
happens to belong to dbus, to assume that it's dbus specific. It's quite |
| 41 |
possible other packages could make use of it too, but don't on your |
| 42 |
system, either because it's a new feature nothing else is using yet, or |
| 43 |
because you simply don't have merged any of the other packages that make |
| 44 |
use of it. |
| 45 |
|
| 46 |
-- |
| 47 |
Duncan - List replies preferred. No HTML msgs. |
| 48 |
"Every nonfree program has a lord, a master -- |
| 49 |
and if you use the program, he is your master." Richard Stallman |
Archives