On Sun, Feb 24, 2013 at 10:39:49PM +0200, Thanos Baloukas wrote: > Hi > > I installed Xulrunner-18.0.1/Firefox-18.0.1 today. > Xulrunner installed most directories and files under > unprivileged user's ownership. If no one else has noticed that, > then I must have done something wrong.
I would expect the ownership to be whoever installed them, and also that an unprivileged user would NOT be able to write to them. I'm not at my desktop at the moment. > > On Firefox-18.0.1, in mozconfig the book has > > #ac_add_options --with-libxul-sdk=\$(pkg-config --variable=sdkdir libxul) > > Is the backslash needed? ISTR I added the backslash, with a comment explaining it, because when I tried pasting what was in the book at that time it fubar'd. From memory, the comment said that the backslash was for pasting (because the mozconfig is now likely to be pasted, we no longer keep a version in the BLFS repo). > > On Firefox, after the command 'make -f client.mk', I think that the files > > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/xpidlyacc.pyc > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/ply/yacc.pyc > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/ply/lex.pyc > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/ply/__init__.pyc > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/xpidllex.pyc > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/xpidl.pyc > /usr/lib/xulrunner-devel-18.0.1/sdk/bin/xpt.pyc > > were installed under unprivileged user's ownership again. The > directories were owned by this user and were created on Xulrunner's > installation. But it's impossible commands that are supposed to > configure and compile to put files in /usr. I installed a lot of > packages today and got tired. The build commands were run as non root, > and the installation commands as root after 'sudo su -'. > > I also found that the files installed by libvpx-v1.1.0 > where not owned by root. The directory > /usr/share/doc/libxcb-1.9/tutorial and its contents too. > > Thanos > Personally, I don't have any belief that sudo is useful for an LFS user. For someone maintaining a production system, with strong restrictions on what they can do, yes there is a use for it. But having tried it while I was reworking my own buildscripts, it's too easy to change it so that your user can do anything, and to allow that with only a password on the first use during the current session. Personally, I'm a heretic - I build my normal packages as root (for new things, I build as a user and do a DESTDIR install to review what gets installed). In theory, as you note, building as a regular user will not let you install things below /usr until you 'su'. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
