betelgeuse@pena ~ $ qlist hal | xargs grep cryptsetup /usr/share/hal/scripts/hal-luks-remove:CRYPTSETUP=/sbin/cryptsetup /usr/share/hal/scripts/hal-luks-setup:CRYPTSETUP=/sbin/cryptsetup /usr/share/hal/scripts/hal-luks-teardown:CRYPTSETUP=/sbin/cryptsetup Every other distribution installs /sbin so we should at least provide a symlink /sbin/crypsetup --> /bin/crypsetup or the other way around. Hal should probably also fix to not hardcode stuff like this but it is not the only one I have come across that had this problem (for example pmount had this before I fixed it there). econf \ --sbindir=/bin \ $(use_enable !dynamic static) \ --libdir=/usr/$(get_libdir) \ $(use_enable nls) \ $(use_enable selinux) \ || die Here we see that it is meant by upstream to go into /sbin.
i'd rather fix sys-fs/cryptsetup-luks to install into /sbin like everyone else was there a specific reason for this Benjamin ?
Yeah there was 2 issues. One upstream puts it in /usr and the second, more relevant issue was that embedded and co started to scream at me when I suggested that I put it, and the libs it relies on, in /sbin, /lib etc. See bug #112597 for a discussion about the lib placement for example. The current situation is not optimal really, for example in my own usage I build it statically and then cp the bin to /sbin for using my scripts as my /usr is encrypted. That said, the reason I did that was the amount of resistance I got from people for adding more things to the / partition. In reality if people are hardcoding this it's that which should be fixed imo, though I'm not against putting it in /sbin and /lib either but there are quite a few deps if we're going to build it in such a way that a dynamic binary will work in /sbin.
Benjamin: There shouldn't be any objections to symlinking then?
There are a few reasons why you might not want to symlink, but nothing to major I can think of off the top of my head.
Benjamin: i meant why is it /bin/cryptsetup and not /sbin/cryptsetup
err cough, i forgot i'd change the sbindir. I had a reason at the time but I can't remember it now. No, I see no reason not to change the sbindir in econf.
Just as a note that currently the pmount ebuild hardcodes /bin/cryptsetup so unless a symlink is done, that should be changed too. Well any way removing the hardcode makes sense any way.
i'd say fix pmount and leave out the symlink in /bin
And that's wrong Mike. Everything expects it in /sbin. We're overriding upstream's placement. Other scripts and programs expect it in /sbin. It's not just pmount.
Just to be clear upstream place it in /usr/sbin. I've modified the ebuild to put it in /sbin and symlink to /bin. Please start fixing the hardpaths as I won't leave the symlink in for that long....
wtf are you talking about Doug ... ive been saying it needs to be in /sbin and not /bin
