On Thu, Jan 19, 2017 at 8:45 AM, Gilles Dartiguelongue wrote:
> Le mercredi 04 janvier 2017 à 21:12 +, Wolfgang Mueller a écrit :
>> is definitely not set when executing cron scripts like that. I
>> deleted all mandoc.db files and waited for them to be regenerated.
>> Only
>> the one in /usr/s
Le mercredi 04 janvier 2017 à 21:12 +, Wolfgang Mueller a écrit :
> is definitely not set when executing cron scripts like that. I
> deleted all mandoc.db files and waited for them to be regenerated.
> Only
> the one in /usr/share/man was generated, which means that makewhatis
> fell back to th
> I have only tested this manually with run-parts, so I shall put it in
> cron.hourly right now and report back later.
MANPATH is definitely not set when executing cron scripts like that. I
deleted all mandoc.db files and waited for them to be regenerated. Only
the one in /usr/share/man was genera
> 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 hap
On Wed, 4 Jan 2017 16:45:56 +
Wolfgang Mueller wrote:
> While working on an mdocml ebuild, I noticed that a call to `makewhatis'
> for mdocml or the corresponding `mandb' call for sys-apps/man-db does
> not create entries for gcc's or binutils' man pages. This is because
> the MANPATH environ
