On 2/27/19 11:22 AM, Douglas R. Reno via blfs-dev wrote:
On 2/27/19 11:16 AM, Bruce Dubbs via blfs-dev wrote:
On 2/27/19 11:04 AM, Douglas R. Reno via blfs-dev wrote:
Hi guys,
I'm doing the pre-installation configuration for KDE Frameworks 5.
I'm building in /opt this time.
For the /usr instructions, we have the following:
cat >> /etc/sudoers.d/qt << "EOF"
|Defaults env_keep += QT_PLUGIN_PATH Defaults env_keep +=
QML2_IMPORT_PATH|
EOF
cat >> /etc/sudoers.d/kde << "EOF"
|Defaults env_keep += KF5_PREFIX|
EOF
Shouldn't we duplicate these instructions in the /opt instructions as
well, so that those variables get defined for the root user when
running under sudo?
I don't recall adding those instructions. In my scripts, I use a
variable SUDO='sudo -E' and use it as $SUDO. More precisely,
if [ $UID -ne 0 ]; then SUDO='sudo -E'; fi
The -E variable
Indicates to the security policy that the user wishes to preserve
their existing environment variables. The security policy may
return an error if the user does not have permission to preserve
the environment
Do we really need this section at all?
-- Bruce
I believe DJ was the one who implemented this. I'm not 100% certain myself.
I don't think that sudo defaults to using -E to pull in all of the
variables - a user would have to specify that themselves, and I'm not
certain that we specify that anywhere.
That is all correct, but by the time a user gets to KDE they should know
that environment variables need to be available when changing to root.
That's a lesson that users need to learn as early as LFS Chapter 2 where
$LFS needs to be defined for root.
Note that a simple su does keep variables by default, but sudo does not.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
