Randy McMurchy wrote:
I'm just saying they don't belong in /usr/sbin.
Agreed wholeheartedly.
Now we just have to convince the masses. :-)
As a "mass" person, I can say that I'm convinced. I've always seen
binaries in /usr/sbin from different packages and wondered whether I
should be able to run them or not.
My concern is determining what goes in /usr/sbin and what goes in
/usr/lib/packagename. Glancing through /usr/sbin on my system for BLFS
packages, I see things such as sshd and usermod that I definitely want
in root's path. What about sftp-server? I'm not sure if that should be
called or not. What about alsaconf and alsactl?
What happens for a certain package when it's determined that some parts
go to sbin and some to lib/packagename? You can only pass one
--libexecdir=. Then are there just going to be a bunch of mv commands
added at the end?
Just some thoughts. I like the I idea, though, and I plan on
implementing it for packages where I'm confident about the above situations.
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
