On 14 January 2014 12:13, Karl Williamson wrote:
> which is incomplete. What has parrot done in the meantime?
Well, as downstream, I found a convenient hack around the problem to
side-step the bad perldoc and just reduce the behaviour to the subset we
needed without the security false alarms
On 11/28/2013 12:20 AM, Kent Fredric wrote:
We've had a lot of problems lately with the fact Parrot uses Perldoc
to simply extract pod statements from a generated file and emit them
into another file.
This stems mostly from the fact perldoc over-zealously drops privs.
But the gist of it is: par
We've had a lot of problems lately with the fact Parrot uses Perldoc
to simply extract pod statements from a generated file and emit them
into another file.
This stems mostly from the fact perldoc over-zealously drops privs.
But the gist of it is: parrot calls `perldoc -ud target source`, and
we
