On Mon, 2009-05-11 at 14:48 +0200, Stephan Kulow wrote:
Am Montag 11 Mai 2009 schrieb Adrian Schröter:
Am Montag, 11. Mai 2009 10:27:03 schrieb CyberOrg:
On Mon, May 11, 2009 at 1:40 PM, Michael Calmer <mc@suse.de> wrote:
Yes, install the application umount.devkit in /usr/sbin ..
If you do this, the [u]mount command will not detect this helper script. So
umount -t devkit ... will not work
[u]mount only searches in /sbin for such helper scripts.
So install in /usr/sbin and symlink in /sbin?
symlink in /sbin would contradict the check. It is there because binaries in /bin and /sbin must not use anything in /usr, because this might not be available at that point of time.
"at that point of time" needs explanation I guess: /usr is possibly mounted later in the boot process, most prominently from a network share. So if devkit is the possible host of a /usr filesystem, all its requirements need to be out of /usr. This doesn't seem to be the case here though.
But this is only the umount command, so it wouldn't be affected by startup. Also, if I change it back to /sbin, and then change; --libexecdir=%{_prefix}/lib/DeviceKit-disks to be; --libexecdir=%{_lib}/DeviceKit-disks ...as well? Would that be enough for it to be officially blessed? Or I am not even allowed to use "%{_datadir}" for the package and need to change that as well? Cheers, Magnus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org