> You shouldn't call those tools inside ebuild. If the build system is > doing that, patch it out. In fact, I'm surprised sandbox doesn't catch > this as an attempt to write outside allowed paths.
Okay, I shall remove any calls to database creation and just alert the user. > Are you sure this happens in cron.daily entries as well? I'd say cron > should be respecting profile environment one way or another. For man-db it does not matter, since it does not use MANPATH to get the right directories (instead uses /etc/man_db.conf). I am quite sure it happens to me with mdocml (without sourcing /etc/profile in the cron.daily script it ignores gcc's and binutils' man pages). I have only tested this manually with run-parts, so I shall put it in cron.hourly right now and report back later. fwiw printing env to a file from a cron.daily script run manually with run-parts results in an environment without MANPATH set. Presumably because it is not a login shell, and /etc/profile is not sourced. -- Wolfgang Mueller / vehk.de / GPG 0xc543cfce9465f573
signature.asc
Description: PGP signature
