On Mon, Jun 17, 2013 at 7:43 PM, Michael Biebl <mbi...@gmail.com> wrote: > I guess we can all agree that the cache file in /etc is not really nice and > that > /etc/ld.so.cache already exists, doesn't really make that better. > A 5+ MB blob is really annoying, especially if you use tools like etckeeper. > Putting the cache files in /lib (or /usr/lib), isn't really great > either, even though we have some precedence here too, like > /lib/modules/*/ or icon and gsettings cache files. > > What about this compromise: > a/ udevadm hwdb --update should be run in postinst, i.e. do not ship a > pre-generated cache file > b/ let udevadm hwdb --update check, if /var or /var/cache is on a > separate partition. > If not, store the cache file in /var/cache/udev, /etc/udev otherwise > c/ update udev to read from both locations, /var/cache having preference > > The only case, where this scheme would fail, is if you backup and > restore a system to a different partitioning scheme.
I agree with Lennart that we don't want this scheme, but rather something predictable. How about Colin's suggestion of putting hwdb.bin (and similar files that cannot always be in /var/cache) in /etc/cache? Or if anyone have the stomach for a huge fight, try to convince everyone of the usefulness of /cache? -t _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel